Version: (using KDE 4.2.96) OS: Linux Installed from: Ubuntu Packages I have seen a lot of similar backtraces from IMAP crashes, but I am only using POP3. I've also found this backtrace here [1], unrelated to the bug report it is attached to. [1] https://bugs.kde.org/show_bug.cgi?id=176688#c17 Other potentially useful info: * I have filters set up, so that some mail coming into the inbox is automatically moved elsewhere. It doesn't look like I received any message when the crash occurred, though. * It is possible that I had a search folder open when I last closed Kontact/KMail. But they don't seem to remain open when KMail is restarted. Will update bug report if I manage to reproduce. Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0xb11a09a6 in FolderStorage::ignoreJobsForMessage (this=0x89339c8, msg=0x9372a68) at /build/buildd/kdepim-4.2.96/kmail/folderstorage.cpp:1113 #6 0xb119f703 in FolderStorage::unGetMsg (this=0x89339c8, idx=0) at /build/buildd/kdepim-4.2.96/kmail/folderstorage.cpp:569 #7 0xb116cfab in KMFolder::unGetMsg (this=0x8951298, idx=0) at /build/buildd/kdepim-4.2.96/kmail/kmfolder.cpp:373 #8 0xb11edbdb in KMSearchPattern::matches (this=0x890c238, serNum=130161, ignoreBody=false) at /build/buildd/kdepim-4.2.96/kmail/kmsearchpattern.cpp:794 #9 0xb119f0a0 in FolderStorage::slotProcessNextSearchBatch (this=0x89339c8) at /build/buildd/kdepim-4.2.96/kmail/folderstorage.cpp:1180 #10 0xb13a80b4 in KMSearch::slotProcessNextBatch (this=0x8971da0) at /build/buildd/kdepim-4.2.96/kmail/kmfoldersearch.cpp:272 #11 0xb13a822b in KMSearch::qt_metacall (this=0x8971da0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfc71cb8) at /build/buildd/kdepim-4.2.96/obj-i486-linux-gnu/kmail/kmfoldersearch.moc:79 #12 0xb5c93ca8 in QMetaObject::activate (sender=0x894d3c0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069 #13 0xb5c94932 in QMetaObject::activate (sender=0x894d3c0, m=0xb5d70904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143 #14 0xb5ccf717 in QTimer::timeout (this=0x894d3c0) at .moc/release-shared/moc_qtimer.cpp:128 #15 0xb5c996fe in QTimer::timerEvent (this=0x894d3c0, e=0xbfc7213c) at kernel/qtimer.cpp:261 #16 0xb5c8e15f in QObject::event (this=0x894d3c0, e=0xbfc7213c) at kernel/qobject.cpp:1082 #17 0xb615ee9c in QApplicationPrivate::notify_helper (this=0x84a5470, receiver=0x894d3c0, e=0xbfc7213c) at kernel/qapplication.cpp:4084 #18 0xb616719e in QApplication::notify (this=0xbfc723e8, receiver=0x894d3c0, e=0xbfc7213c) at kernel/qapplication.cpp:3631 #19 0xb6d854dd in KApplication::notify (this=0xbfc723e8, receiver=0x894d3c0, event=0xbfc7213c) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302 #20 0xb5c7da3b in QCoreApplication::notifyInternal (this=0xbfc723e8, receiver=0x894d3c0, event=0xbfc7213c) at kernel/qcoreapplication.cpp:602 #21 0xb5cacd71 in QTimerInfoList::activateTimers (this=0x8493334) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #22 0xb5ca94e0 in timerSourceDispatch (source=0x8493300) at kernel/qeventdispatcher_glib.cpp:164 #23 0xb4d42b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb4d460eb in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb4d46268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb5ca9438 in QEventDispatcherGlib::processEvents (this=0x8473028, flags={i = -1077468488}) at kernel/qeventdispatcher_glib.cpp:323 #27 0xb6200365 in QGuiEventDispatcherGlib::processEvents (this=0x8473028, flags={i = -1077468440}) at kernel/qguieventdispatcher_glib.cpp:202 #28 0xb5c7c06a in QEventLoop::processEvents (this=0xbfc72360, flags={i = -1077468376}) at kernel/qeventloop.cpp:149 #29 0xb5c7c4aa in QEventLoop::exec (this=0xbfc72360, flags={i = -1077468312}) at kernel/qeventloop.cpp:200 #30 0xb5c7e959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #31 0xb615ed17 in QApplication::exec () at kernel/qapplication.cpp:3553 #32 0x0804bfef in main (argc=3, argv=0xbfc726e4) at /build/buildd/kdepim-4.2.96/kontact/src/main.cpp:218
*** Bug 176688 has been marked as a duplicate of this bug. ***
*** Bug 199892 has been marked as a duplicate of this bug. ***
*** Bug 194990 has been marked as a duplicate of this bug. ***
*** Bug 202367 has been marked as a duplicate of this bug. ***
*** Bug 186422 has been marked as a duplicate of this bug. ***
*** Bug 204678 has been marked as a duplicate of this bug. ***
*** Bug 205296 has been marked as a duplicate of this bug. ***
*** Bug 205451 has been marked as a duplicate of this bug. ***
*** Bug 205986 has been marked as a duplicate of this bug. ***
*** Bug 207046 has been marked as a duplicate of this bug. ***
*** Bug 207262 has been marked as a duplicate of this bug. ***
*** Bug 203703 has been marked as a duplicate of this bug. ***
*** Bug 200626 has been marked as a duplicate of this bug. ***
*** Bug 208123 has been marked as a duplicate of this bug. ***
With a bit of luck, this problem could be fixed in KDE 4.3.2, a potential fix has been committed in r1024448, see http://websvn.kde.org/?revision=1024448&view=revision .
*** Bug 208585 has been marked as a duplicate of this bug. ***
*** Bug 210017 has been marked as a duplicate of this bug. ***
According to the reporter of our downstream bug for this (https://launchpad.net/bugs/420337) this has not been an issue for him in KDE 4.3.2, and Kontact has been quite stable for him. (I think he's CC'd here in fact)