Bug 322333

Summary:	Mail filter crashed on manual apply
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Maarten ter Huurne <maarten>
Component:	Mail Filter Agent	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	amantia
Priority:	NOR
Version First Reported In:	4.10
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Maarten ter Huurne 2013-07-14 09:48:40 UTC

Application: akonadi_mailfilter_agent (4.10)
KDE Platform Version: 4.10.5 "release 4"
Qt Version: 4.8.4
Operating System: Linux 3.4.47-2.38-desktop x86_64
Distribution (Platform): openSUSE RPMs

-- Information about the crash:
- What I was doing when the application crashed:

I added a new client-side mail filter, selected a range of emails in my inbox and pressed Ctrl-J to re-filter the selected emails. Very soon after that the crash handler dialog popped up.

Looking at the backtrace, this crash might not have been the original filter that crashed, but the automatically restarted mail filter process after the previous filter died. I get quite a lot of Akonadi automatic process restarts, unfortunately, although usually it is akonadi_mixedmaildir_resource that has problems, not akonadi_mailfilter_agent.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Mail Filter Agent (akonadi_mailfilter_agent), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  deref (this=0x0) at /usr/include/QtCore/qatomic_x86_64.h:133
#7  operator= (l=..., this=0x111fe28) at /usr/include/QtCore/qlist.h:442
#8  QList<Akonadi::Item>::clear (this=0x111fe28) at /usr/include/QtCore/qlist.h:766
#9  0x00007fb7f2f7421f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x00007fb7f2f7352c in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#11 0x00007fb7f152785c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#12 0x00007fb7f152bcda in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#13 0x00007fb7f40125e6 in KApplication::notify (this=0x7fffe5de5df0, receiver=0x10c4a20, event=0x7fffe5de5af0) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311
#14 0x00007fb7f2f5ed1e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#15 0x00007fb7f2f8fac1 in ?? () from /usr/lib64/libQtCore.so.4
#16 0x00007fb7f2f8cbd4 in ?? () from /usr/lib64/libQtCore.so.4
#17 0x00007fb7f2f8cbf1 in ?? () from /usr/lib64/libQtCore.so.4
#18 0x00007fb7ea4a43b5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fb7ea4a46e8 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fb7ea4a47a4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fb7f2f8d236 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#22 0x00007fb7f15c7bee in ?? () from /usr/lib64/libQtGui.so.4
#23 0x00007fb7f2f5da6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x00007fb7f2f5dcf8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007fb7f2f62998 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#26 0x00007fb7f3588143 in Akonadi::AgentBase::init (r=0xd7abf0) at /usr/src/debug/kdepimlibs-4.10.5/akonadi/agentbase.cpp:584
#27 0x00000000004182f3 in ?? ()
#28 0x00007fb7f0aa7455 in __libc_start_main () from /lib64/libc.so.6
#29 0x000000000040bcb5 in _start ()

Possible duplicates by query: bug 322293, bug 320556, bug 320344, bug 319465, bug 319441.

Reported using DrKonqi

Comment 1 András Manţia 2013-11-16 12:43:34 UTC

Unfortunately I cannot reproduce and the attached backtrace doesn't help to identify the problem. In case you run into this again and can reproduce, please reopen the report.