Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.3 Operating System: Linux 2.6.30-gentoo-r5 x86_64 What I was doing when the application crashed: sadly I have no additional info - aside from the crash report. -- Backtrace: Application: Kontact (kontact), signal: Aborted [KCrash Handler] #5 0x00007f7ead939205 in raise () from /lib/libc.so.6 #6 0x00007f7ead93a723 in abort () from /lib/libc.so.6 #7 0x00007f7eae671295 in qt_message_output (msgType=QtFatalMsg, buf=<value optimized out>) at global/qglobal.cpp:2042 #8 0x00007f7eae6713b0 in qFatal (msg=<value optimized out>) at global/qglobal.cpp:2241 #9 0x00007f7e9cf72d23 in KMail::MessageListView::Core::Model::applyFilterToSubtree (this=0x1503b60, item=0x2ff41b0, parentIndex=@0x7fff95188890) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:348 #10 0x00007f7e9cf7902e in KMail::MessageListView::Core::Model::setFilter (this=0x1503b60, filter=<value optimized out>) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/model.cpp:340 #11 0x00007f7e9cfa108c in KMail::MessageListView::Core::Widget::searchTimerFired (this=0x14b87c0) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2/kmail/messagelistview/core/widgetbase.cpp:1130 #12 0x00007f7e9cc68963 in KMail::MessageListView::Core::Widget::qt_metacall (this=0x14b87c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff95188a30) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/moc_widgetbase.cpp:119 #13 0x00007f7e9cc68a75 in KMail::MessageListView::Widget::qt_metacall (this=0x698e, _c=27022, _id=6, _a=0xffffffffffffffff) at /var/tmp/portage/kde-base/kmail-4.3.2/work/kmail-4.3.2_build/kmail/moc_widget.cpp:75 #14 0x00007f7eae76beb9 in QMetaObject::activate (sender=0x2b0aad0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xffffffffffffffff) at kernel/qobject.cpp:3101 #15 0x00007f7eae7667b3 in QObject::event (this=0x2b0aad0, e=0x698e) at kernel/qobject.cpp:1066 #16 0x00007f7eaf4fb6dd in QApplicationPrivate::notify_helper (this=0x64a590, receiver=0x2b0aad0, e=0x7fff95189100) at kernel/qapplication.cpp:4065 #17 0x00007f7eaf50400e in QApplication::notify (this=0x7fff95189440, receiver=0x2b0aad0, e=0x7fff95189100) at kernel/qapplication.cpp:4030 #18 0x00007f7eb02cb341 in KApplication::notify (this=0x7fff95189440, receiver=0x2b0aad0, event=0x7fff95189100) at /var/tmp/portage/kde-base/kdelibs-4.3.2-r2/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302 #19 0x00007f7eae756d53 in QCoreApplication::notifyInternal (this=0x7fff95189440, receiver=0x2b0aad0, event=0x7fff95189100) at kernel/qcoreapplication.cpp:606 #20 0x00007f7eae780c46 in QTimerInfoList::activateTimers (this=0x636440) at kernel/qcoreapplication.h:213 #21 0x00007f7eae77de7d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165 #22 0x00007f7ea9d36f41 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0x00007f7ea9d3a4d8 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #24 0x00007f7ea9d3a68c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0x00007f7eae77ddef in QEventDispatcherGlib::processEvents (this=0x634630, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:328 #26 0x00007f7eaf58728f in QGuiEventDispatcherGlib::processEvents (this=0x698e, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #27 0x00007f7eae755a12 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1793551504}) at kernel/qeventloop.cpp:149 #28 0x00007f7eae755bac in QEventLoop::exec (this=0x7fff951893b0, flags={i = -1793551424}) at kernel/qeventloop.cpp:197 #29 0x00007f7eae75a526 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #30 0x000000000040405a in main (argc=1, argv=0x7fff95189958) at /var/tmp/portage/kde-base/kontact-4.3.2/work/kontact-4.3.2/kontact/src/main.cpp:218 This bug may be a duplicate of or related to bug 211046 Reported using DrKonqi
Merging with bug 186220. Thanks *** This bug has been marked as a duplicate of bug 186220 ***