After reboot kontact can't be started

Bug #470528 reported by hyper_ch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE PIM
Invalid
High
kdepim (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: kdepim

I installed yesterday Kubuntu Karmic and it works fine.

However after a reboot I can't start Kontact anymore. I keep getting this
output when issued "kontact &" from the terminal:

Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
QObject::connect: Cannot queue arguments of type 'KParts::WindowArgs'
(Make sure 'KParts::WindowArgs' is registered using qRegisterMetaType().)
<unknown program name>(4370)/: Communication problem with "kontact" , it
probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "

However I can run Kmail, Akregator, Korganizer just fine as stand-alone. Also, when I delete the configs and keep adding one after the other again (like first akregator then kmail and kaddressbook and finally korganizer it works again.

Tags: crash kontact
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Can you get a backtrace please?

Changed in kdepim (Ubuntu):
status: New → Incomplete
Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

Well, I would supply you with a backtrace if I could figure out how to get one.

I tried to "gdb kontact" --> "run"

And then back at the gdb command prompt I run "bt" but only "No stack." was returned.

Although when I run Kontact from the KMenu I don't get to a point where the KDE Crash Application tool (I keep forgetting its name) appears.

Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

I have now achieved a backtrace and I cut the output of backtrace full after the first several hundred lines. It was in a loop and just continued to print out the same lines time and again. For me it doesn't tell anything but I hope it'll be usefull for others.

Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

Ok, I was told in the #kontact channel on freenode that this backtrace above is useless and that I should first install the kdepim-dbg package.

I have done so now and have here the new output.

Changed in kdepim (Ubuntu):
importance: Undecided → Low
status: Incomplete → Triaged
Revision history for this message
hyper_ch (bugs-launchpad-net-roleplayer) wrote :

I downgraded now to the official ubuntu packages and kontact works just fine there.

Revision history for this message
Christophe Giboudeaux (krop) wrote :

The crash was caused by a incompatible Qt version.

Changed in kdepim (Ubuntu):
status: Triaged → Invalid
Changed in kdepim:
status: Unknown → Invalid
Changed in kdepim:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.