Version: 1.10.1 (using 4.1.2 (KDE 4.1.2) "release 44.2", KDE:KDE4:Factory:Desktop / openSUSE_10.3) Compiler: gcc OS: Linux (i686) release 2.6.22.18-0.2-bigsmp What I did: I was just browsing through my IMAP account folders, when KMail crashed. Just like that, out of the blue. Not sure how to reproduce it, but some kind of backtrace is attached.
Created attachment 27988 [details] Backtrace of Kmail crash
copy/paste from #1 : Anwendung: Kontact (kontact), Signal SIGSEGV [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb4c716d0 (LWP 4556)] [KCrash handler] #6 0xb14cd8d9 in KMFolder::open () from /usr/lib/libkmailprivate.so.4 #7 0xb16873e2 in KMCommand::keepFolderOpen () from /usr/lib/libkmailprivate.so.4 #8 0xb1697f58 in KMCommand::slotStart () from /usr/lib/libkmailprivate.so.4 #9 0xb168cbd7 in KMCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4 #10 0xb168d382 in KMReplyToAllCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4 #11 0xb7e68c19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb7e692e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb7e6f817 in QSingleShotTimer::timeout () from /usr/lib/libQtCore.so.4 #14 0xb7e6f93c in QSingleShotTimer::timerEvent () from /usr/lib/libQtCore.so.4 #15 0xb7e6373a in QObject::event () from /usr/lib/libQtCore.so.4 #16 0xb58811cc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #17 0xb5885c79 in QApplication::notify () from /usr/lib/libQtGui.so.4 #18 0xb796ad6d in KApplication::notify () from /usr/lib/libkdeui.so.5 #19 0xb7e53cb9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #20 0xb7e82821 in QTimerInfoList::activateTimers () from /usr/lib/libQtCore.so.4 #21 0xb7e7f260 in ?? () from /usr/lib/libQtCore.so.4 #22 0xb52055d6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0xb5208972 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0x08063cf8 in ?? () #25 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall () *** This bug has been marked as a duplicate of bug 117415 ***