kontact crashed with SIGSEGV

[Ender Aysal]

Binary package hint: kdepim

ProblemType: Crash
Architecture: i386
Disassembly: 0xb80d4430:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/kontact
Package: kontact 4:4.1.1a-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: kontact -session 106b697474000122007187000000106590023_1220074084_977044
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 LANGUAGE=de
Signal: 11
SourcePackage: kdepim
Stacktrace: #0 0xb80d4430 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: kontact crashed with SIGSEGV
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare vboxusers video

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Xosé (ubuntu-galizaweb)]

It crashes at startup - always.

[Andreas Moog (ampelbein)]

Thanks. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[laksdjfaasdf (laksdjfaasdf)]

Got the same error - it always happens when starting kontact. When I have time I will do a backtrace. The error messages in console when starting kontact:

kontact(8762)/kmail KMailPart::KMailPart: InstanceName: "kontact"
kontact(8762)/kmail KMailPart::KMailPart: InstanceName: "kontact"
kontact(8762)/kmail KMail::lockOrDie: oldPid= 13497
kontact(8762)/kmail KMKernel::KMKernel:
kontact(8762): The kwalletd service has been disabled
kontact(8762): The kwalletd service has been disabled
kontact(8762): The kwalletd service has been disabled
kontact(8762): The kwalletd service has been disabled
kontact(8762): The kwalletd service has been disabled
kontact(8762): The kwalletd service has been disabled
kontact(8762)/kmail KMKernel::init: foldersPath (from config): "/home/felix/Mail"
kontact(8762)/kmail KMKernel::identityManager:
kontact(8762)/kmail KMFilterMgr::KMFilterMgr: pPopFilter set
kontact(8762)/kmail KMFolderMaildir::createIndexFromContents: Creating index for "/home/felix/.kde/share/apps/kmail/autosave"
kontact(8762)/kmail KMFolderMaildir::createIndexFromContents: Creating index for "/home/felix/.kde/share/apps/kmail/autosave"
kontact(8762)/kmail KMFolderImap::slotListNamespaces: Waiting for connection
kontact(8762)/kmail KMFolderImap::slotListNamespaces: Waiting for connection
kontact(8762)/kmail KMFolderImap::slotListNamespaces: Waiting for connection
kontact(8762)/kmail KMFolderImap::slotListNamespaces: Waiting for connection
kontact(8762)/kmail KMFolderImap::slotListNamespaces: Waiting for connection
kontact(8762)/kmail KMSystemTray::KMSystemTray: Initting systray
kontact(8762)/kmail KMSystemTray::setMode: Setting systray mMode to 0
kontact(8762)/kmail KMailPart::guiActivateEvent:
kontact(8762)/kmail KMailPart::guiActivateEvent:
kontact(8762)/kmail KMailPart::guiActivateEvent:
*** KMail got signal 11 (Crashing)
KCrash: Application 'kontact' crashing...
<unknown program name>(8759)/: 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)" "

[Hein van Rensburg (hvralpha)]

Was busy establishing settings in kmail ( A custom time format) when crash occurred

[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!

A backtrace for the original crash was never provided. Due to the sparse description it's probably impossible to tell whether the other crashes reported here are the same.