Kontact crashes with DBus error message

[laksdjfaasdf]

Binary package hint: kontact

Jaunty (update from Intrepid + updates 2008-01-22

Description:

I have several IMAP accounts where one server is currently not available. When starting kontact it crashes with a DBus error message. Included is a Valgrind report.

$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log kontactCalling 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.
<unknown program name>(6551)/: Communication problem with "kontact" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive areply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

$ kontact(6554) Sonnet::Loader::loadPlugin: Successfully loaded plugin: "kspell_hspell.desktop"
kontact(6554) Sonnet::Loader::loadPlugin: Successfully loaded plugin: "kspell_enchant.desktop"

[laksdjfaasdf (laksdjfaasdf)]

Valgrind report for kontact 4:4.1.96-0ubuntu2

[Philippe Clérié (pclerie)]

I confirm this bug. I have the same problem on 4.2 intrepid packages downloaded today.

A question: is kmail currently using Akonadi for storage? If it does I need to revise my backup procedures.

Philippe

[Jonathan Thomas (echidnaman)]

If this is still a problem with KDE 4.2.0, could you please get a backtrace from gdb? Thanks.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!