Application that crashed: kontact Version of the application: 4.3.3 KDE Version: 4.3.3 (KDE 4.3.3) Qt Version: 4.5.2 Operating System: Linux 2.6.31-14-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Created a new filter and went to an online imap folder (googlemail account). Hit [Ctrl]+[j] to apply all filters. The new filter's rule is a very simple regular expression (^\[bug \d*\]) that should move all KDE and Kubuntu related bugs to a designated subfolder. The crash happend when I accessed the destination folder to see if the messages have been moved there. expected result: - the matching messages are moved to the desired folder - Kontact keeps running actual result: - the matching messages are moved to the desired folder - Kontact crashed shortly after accessing the folder -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x732d746c in ?? () #7 0xb47706c9 in KMReaderWin::displayMessage (this=0x4e) at ../../kmail/kmreaderwin.cpp:1608 #8 0xb47708bb in KMReaderWin::updateReaderWin (this=0x9d33080) at ../../kmail/kmreaderwin.cpp:1548 #9 0xb477ee74 in KMReaderWin::qt_metacall (this=0x9d33080, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfb7099c) at ./kmreaderwin.moc:168 #10 0x0439e263 in QMetaObject::activate (sender=0x9d330d8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #11 0x0439eec2 in QMetaObject::activate (sender=0x9d330d8, m=0x4479904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #12 0x043d8667 in QTimer::timeout (this=0x9d330d8) at .moc/release-shared/moc_qtimer.cpp:128 #13 0x043a39ae in QTimer::timerEvent (this=0x9d330d8, e=0xbfb70e30) at kernel/qtimer.cpp:261 #14 0x043983bf in QObject::event (this=0x9d330d8, e=0xbfb70e30) at kernel/qobject.cpp:1075 #15 0x00b88f54 in QApplicationPrivate::notify_helper (this=0x9743040, receiver=0x9d330d8, e=0xbfb70e30) at kernel/qapplication.cpp:4056 #16 0x00b9067c in QApplication::notify (this=0xbfb71194, receiver=0x9d330d8, e=0xbfb70e30) at kernel/qapplication.cpp:3603 #17 0x0039a14a in KApplication::notify (this=0xbfb71194, receiver=0x9d330d8, event=0xbfb70e30) at ../../kdeui/kernel/kapplication.cpp:302 #18 0x043886cb in QCoreApplication::notifyInternal (this=0xbfb71194, receiver=0x9d330d8, event=0xbfb70e30) at kernel/qcoreapplication.cpp:610 #19 0x043b57ce in QCoreApplication::sendEvent (this=0x973887c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 QTimerInfoList::activateTimers (this=0x973887c) at kernel/qeventdispatcher_unix.cpp:572 #21 0x043b30e0 in timerSourceDispatch (source=0x9738848) at kernel/qeventdispatcher_glib.cpp:165 #22 0x0192ee78 in g_main_dispatch (context=0x9737910) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:1960 #23 IA__g_main_context_dispatch (context=0x9737910) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2513 #24 0x01932720 in g_main_context_iterate (context=0x9737910, block=<value optimized out>, dispatch=1, self=0x9749a00) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2591 #25 0x01932853 in IA__g_main_context_iteration (context=0x9737910, may_block=1) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2654 #26 0x043b302c in QEventDispatcherGlib::processEvents (this=0x970b9f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #27 0x00c29be5 in QGuiEventDispatcherGlib::processEvents (this=0x970b9f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #28 0x04386c79 in QEventLoop::processEvents (this=0xbfb710f4, flags=) at kernel/qeventloop.cpp:149 #29 0x043870ca in QEventLoop::exec (this=0xbfb710f4, flags=...) at kernel/qeventloop.cpp:201 #30 0x0438953f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #31 0x00b88dd7 in QApplication::exec () at kernel/qapplication.cpp:3525 #32 0x0804b4e6 in main (argc=1, argv=0xbfb713b4) at ../../../kontact/src/main.cpp:218 This bug may be a duplicate of or related to bug 208012 Reported using DrKonqi
This crash is bug 180741. Can you please read https://bugs.kde.org/show_bug.cgi?id=180741#c41 and check the situations ? Thanks
Waiting for feedback. Marking as NEEDSINFO.
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!