Application: akonadi_mailfilter_agent (4.10) KDE Platform Version: 4.10.1 Qt Version: 4.8.4 Operating System: Linux 3.7.10-gentoo x86_64 Distribution: "Gentoo Base System release 2.1" -- Information about the crash: - What I was doing when the application crashed: I had sent an email and wasn't doing anything in Kmail any more. - Unusual behavior I noticed: When I compose a new email, there's a yellow warning at the top saying that the akonadi desktop indexer is not running. When I click on "configure" in that box, the dialog window that pops up says that it is running and indexing or "ready". Also, kmail-4.10.1 is somewhat slower than the previous kmail-4.9.5. This crash never occurred in kmail-4.9.5 Additionally, I suspect that this is related to the filter rules of the type, "If To is not in the address book", with action "Add to address book". In the previous kmail-4.9.5 this added lots of addresses many times (or added names with no addresses), I have reported a bug about this. Maybe in kmail-4.10.1 this is now "fixed" so that it no longer produces duplicates, but crashes instead? -- Backtrace: Application: Sähköpostisuodatin (akonadi_mailfilter_agent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 deref (this=0x382f4c6f51434963) at /usr/include/qt4/QtCore/qatomic_x86_64.h:133 #7 operator= (l=..., this=0x186e1d8) at /usr/include/qt4/QtCore/qlist.h:442 #8 clear (this=0x186e1d8) at /usr/include/qt4/QtCore/qlist.h:766 #9 timeout (this=0x186e180) at /tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1/akonadi/itemfetchjob.cpp:73 #10 Akonadi::ItemFetchJob::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1_build/akonadi/moc_itemfetchjob.cpp:57 #11 0x00007fa017917441 in QMetaObject::activate (sender=0x18356c0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539 #12 0x00007fa01791c319 in QObject::event (this=0x18356c0, e=<optimized out>) at kernel/qobject.cpp:1156 #13 0x00007fa015e58cd4 in notify_helper (e=0x7fff14948910, receiver=0x18356c0, this=0x1569420) at kernel/qapplication.cpp:4562 #14 QApplicationPrivate::notify_helper (this=0x1569420, receiver=0x18356c0, e=0x7fff14948910) at kernel/qapplication.cpp:4534 #15 0x00007fa015e5da33 in QApplication::notify (this=0x7fff14948c40, receiver=0x18356c0, e=0x7fff14948910) at kernel/qapplication.cpp:4423 #16 0x00007fa018a8f428 in KApplication::notify (this=0x7fff14948c40, receiver=0x18356c0, event=0x7fff14948910) at /tmp/portage/kde-base/kdelibs-4.10.1-r1/work/kdelibs-4.10.1/kdeui/kernel/kapplication.cpp:311 #17 0x00007fa01790330b in QCoreApplication::notifyInternal (this=0x7fff14948c40, receiver=0x18356c0, event=0x7fff14948910) at kernel/qcoreapplication.cpp:946 #18 0x00007fa0179346aa in sendEvent (event=0x7fff14948910, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #19 QTimerInfoList::activateTimers (this=0x15692d0) at kernel/qeventdispatcher_unix.cpp:622 #20 0x00007fa017931f5d in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186 #21 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180 #22 0x00007fa017931f91 in idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:233 #23 0x00007fa00f0ac8fa in g_main_dispatch (context=0x156af30) at gmain.c:2539 #24 g_main_context_dispatch (context=0x156af30) at gmain.c:3075 #25 0x00007fa00f0acc58 in g_main_context_iterate (context=0x156af30, block=1, dispatch=1, self=<optimized out>) at gmain.c:3146 #26 0x00007fa00f0acd0c in g_main_context_iteration (context=0x156af30, may_block=1) at gmain.c:3207 #27 0x00007fa0179326d6 in QEventDispatcherGlib::processEvents (this=0x152aad0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #28 0x00007fa015efd006 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00007fa017901db2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #30 0x00007fa017902037 in QEventLoop::exec (this=0x7fff14948bb0, flags=...) at kernel/qeventloop.cpp:204 #31 0x00007fa017906f25 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #32 0x00007fa017f49a63 in Akonadi::AgentBase::init (r=0x1717320) at /tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1/akonadi/agentbase.cpp:584 #33 0x0000000000419776 in Akonadi::AgentBase::init<MailFilterAgent> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/agentbase.h:343 #34 0x00007fa0153d24cc in __libc_start_main (main=0x40c740 <main(int, char**)>, argc=3, ubp_av=0x7fff14948d58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff14948d48) at libc-start.c:226 #35 0x000000000040c7b5 in _start () Possible duplicates by query: bug 313229, bug 312605, bug 308858, bug 307188, bug 304748. Reported using DrKonqi
Created attachment 78735 [details] New crash information added by DrKonqi akonadi_mailfilter_agent (4.10) on KDE Platform 4.10.1 using Qt 4.8.4 - What I was doing when the application crashed: Nothing, I was away from my computer and the screen was locked. Probably this crash was triggered by an email arriving on an IMAP account. -- Backtrace (Reduced): #7 operator= (l=..., this=0x1730118) at /usr/include/qt4/QtCore/qlist.h:442 #8 clear (this=0x1730118) at /usr/include/qt4/QtCore/qlist.h:766 #9 timeout (this=0x17300c0) at /tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1/akonadi/itemfetchjob.cpp:73 #10 Akonadi::ItemFetchJob::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1_build/akonadi/moc_itemfetchjob.cpp:57 [...] #12 0x00007f7f28bf5319 in QObject::event (this=0x162efd0, e=<optimized out>) at kernel/qobject.cpp:1156
Created attachment 79391 [details] New crash information added by DrKonqi akonadi_mailfilter_agent (4.10) on KDE Platform 4.10.1 using Qt 4.8.4 - What I was doing when the application crashed: I was away from my computer. Probably an arriving email on IMAP has triggered this. -- Backtrace (Reduced): #7 operator= (l=..., this=0x1235e08) at /usr/include/qt4/QtCore/qlist.h:442 #8 clear (this=0x1235e08) at /usr/include/qt4/QtCore/qlist.h:766 #9 timeout (this=0x1235db0) at /tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1/akonadi/itemfetchjob.cpp:73 #10 Akonadi::ItemFetchJob::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1_build/akonadi/moc_itemfetchjob.cpp:57 [...] #12 0x00007fe9acf34319 in QObject::event (this=0xf72020, e=<optimized out>) at kernel/qobject.cpp:1156
Created attachment 79416 [details] New crash information added by DrKonqi akonadi_mailfilter_agent (4.10) on KDE Platform 4.10.1 using Qt 4.8.4 - What I was doing when the application crashed: I was away from my computer, this was probably triggered by an email arriving on IMAP. -- Backtrace (Reduced): #7 operator= (l=..., this=0xbcd588) at /usr/include/qt4/QtCore/qlist.h:442 #8 clear (this=0xbcd588) at /usr/include/qt4/QtCore/qlist.h:766 #9 timeout (this=0xbcd530) at /tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1/akonadi/itemfetchjob.cpp:73 #10 Akonadi::ItemFetchJob::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1_build/akonadi/moc_itemfetchjob.cpp:57 [...] #12 0x00007f42d70d2319 in QObject::event (this=0xbc14f0, e=<optimized out>) at kernel/qobject.cpp:1156
These crashes seems to originate from using synchronous job in SearchRuleString::matchesInternal(), case FuncIsInAddressbook.
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.