kmail crashed with SIGSEGV in KMail::SearchJob::searchCompleteFolder()

[Rocco]

Binary package hint: kdepim

<unknown program name>(2716)/: Communication problem with "kmail" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

in konsole when kmail tries to start.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Oct 22 19:41:12 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kmail
NonfreeKernelModules: nvidia
Package: kmail 4:4.3.2-0ubuntu6
ProcCmdline: kmail
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/tcsh
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7fa89674a46c <_ZN5KMail9SearchJob20searchCompleteFolderEv+300>: mov (%rsi),%rax
 PC (0x7fa89674a46c) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdepim
StacktraceTop:
 KMail::SearchJob::searchCompleteFolder (
 KMFolderImap::search (this=0x1fb0000,
 KMSearch::slotProcessNextBatch (this=0x212c320)
 KMSearch::qt_metacall (this=0x212c320,
 QMetaObject::activate (sender=0x20efcf0,
Title: kmail crashed with SIGSEGV in KMail::SearchJob::searchCompleteFolder()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:2462): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:KMail::SearchJob::searchCompleteFolder (
KMFolderImap::search (this=0x1fb0000,
KMSearch::slotProcessNextBatch (this=0x212c320)
KMSearch::qt_metacall (this=0x212c320,
QMetaObject::activate ()

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!