Version: 1.10.92 (svn rev. 901947) (using Devel) Compiler: gcc 4.3.2 OS: Linux Installed from: Compiled sources kmail crashes when opening one of my IMAP inboxes. This is a fairly large IMAP folder (roughly 9000 messages), served by dovecot 1.2a5. Backtrace: #0 0xffffe424 in __kernel_vsyscall () #1 0x4c390426 in raise () from /lib/libpthread.so.0 #2 0xb7e64714 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 #3 0x000035e6 in ?? () #4 0xbffa3084 in ?? () #5 0x092e2528 in ?? () #6 0x481ba444 in QMainWindow::event () from /usr/lib/libQtGui.so.4 #7 0xbffa2d7c in ?? () #8 0xb5de3548 in ?? () #9 0x00000037 in ?? () #10 0x4c1e0c3d in ?? () from /lib/ld-linux.so.2 #11 0x00000037 in ?? () #12 0x4c1e0c3d in ?? () from /lib/ld-linux.so.2 #13 0xb6243812 in ?? () from /usr/lib/libmimelib.so.4 #14 0x4c1f3fc0 in ?? () from /lib/ld-linux.so.2 #15 0xbffa2e8c in ?? () #16 0xb5de3548 in ?? () #17 0x00000037 in ?? () #18 0xb7e643c9 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 #19 <signal handler called> #20 0x00000006 in ?? () #21 0xb7520cb5 in KMFolderImap::slotListFolderResult () from /usr/lib/libkmailprivate.so.4 #22 0xb7524391 in KMFolderImap::qt_metacall () from /usr/lib/libkmailprivate.so.4 #23 0x46dc2601 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #24 0x46dc3385 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #25 0xb7ae46f5 in KJob::result () from /usr/lib/libkdecore.so.5 #26 0xb7c31e88 in typeinfo for KCompositeJob () from /usr/lib/libkdecore.so.5 #27 0x00000003 in ?? () #28 0xbffa3670 in ?? () #29 0x097f37b8 in ?? () #30 0xb6e6c046 in KIO::Scheduler::jobFinished () from /usr/lib/libkio.so.5 #31 0xb6dc2319 in KIO::SimpleJobPrivate::slaveDone () from /usr/lib/libkio.so.5 #32 0x00000000 in ?? ()
Unfortunately, your backtrace is useless without debug symbols. Please recompile kdepimlibs and kdepim with the debug symbols to provide a better bt. More informations on this page : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
The backtrace is from kdelibs, kdepimlibs and kdepim built with debug info. Looks like something is corrupting the stack. Triggering this crash in kmail -nofork started from within gdb triggers very strange behavior as well: [arklinux@localhost ~]$ gdb kmail GNU gdb Ark Linux (6.8-1ark) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (gdb) set args -nofork (gdb) run Starting program: /usr/bin/kmail -nofork Object::connect: No such signal OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceOnlineChanged(QString,bool) "/usr/bin/kmail(4363)" Error in thread 3083548416 : "org.freedesktop.DBus.Error.UnknownObject - No such object path '/org/soprano/Server'" "/usr/bin/kmail(4363)" Error in thread 3083548416 : "QLocalSocket::connectToServer: Invalid name" kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderImap::setImapPath: ignoring empty path [New LWP 4415] kmail(4363) KMFolderImap::setImapPath: ignoring empty path kmail(4363) KMFolderIndex::updateIndexStreamPtr: utime( "/home/arklinux/.kde/share/apps/kmail/imap/.1599001121.directory/.cron-output.index.ids" , 0) failed (KMMsgDict::getFolderIdsLocation( *this )) kmail(4363) KMFolderIndex::updateIndexStreamPtr: utime( "/home/arklinux/.kde/share/apps/kmail/imap/.1599001121.directory/.cron-output.index.ids" , 0) failed (KMMsgDict::getFolderIdsLocation( *this )) kmail(4363) KMFolderImap::setImapPath: ignoring empty path [LWP 4415 exited] [New process 4363] linux-nat.c:1152: internal-error: linux_nat_resume: Assertion `lp != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) Please answer y or n. linux-nat.c:1152: internal-error: linux_nat_resume: Assertion `lp != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) n linux-nat.c:1152: internal-error: linux_nat_resume: Assertion `lp != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable.
This may be duplicated/related to bug 180554 (same situation and similar backtrace (at least the same function before crashing))
*** This bug has been marked as a duplicate of bug 179765 ***