Bug 339431 - mail filter agent segfaults on kmail startup
Summary: mail filter agent segfaults on kmail startup
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: misc (show other bugs)
Version: 4.14.0
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-26 14:09 UTC by Alexander
Modified: 2018-01-31 16:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2014-09-26 14:09:12 UTC
Application: akonadi_mailfilter_agent (4.14)
KDE Platform Version: 4.14.1
Qt Version: 4.8.6
Operating System: Linux 3.12-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:
Just starting kmail. It usually happens when there are a lot new mails.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Mail Filter Agent (akonadi_mailfilter_agent), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007fca63a918ac in ?? () from /usr/lib/libakonadi-kde.so.4
#7  0x00007fca6339ac5c in QMetaObject::activate (sender=0x15d8390, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3567
#8  0x00007fca6339f193 in QObject::event (this=0x15d8390, e=<optimized out>) at kernel/qobject.cpp:1253
#9  0x00007fca61aca31c in QApplicationPrivate::notify_helper (this=this@entry=0xff49e0, receiver=receiver@entry=0x15d8390, e=e@entry=0x7fffaf7f6170) at kernel/qapplication.cpp:4570
#10 0x00007fca61ad0e18 in QApplication::notify (this=this@entry=0x7fffaf7f6470, receiver=receiver@entry=0x15d8390, e=e@entry=0x7fffaf7f6170) at kernel/qapplication.cpp:4356
#11 0x00007fca6455f13a in KApplication::notify (this=0x7fffaf7f6470, receiver=0x15d8390, event=0x7fffaf7f6170) at ../../kdeui/kernel/kapplication.cpp:311
#12 0x00007fca63385cad in QCoreApplication::notifyInternal (this=0x7fffaf7f6470, receiver=0x15d8390, event=event@entry=0x7fffaf7f6170) at kernel/qcoreapplication.cpp:955
#13 0x00007fca633b77ab in sendEvent (event=0x7fffaf7f6170, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#14 QTimerInfoList::activateTimers (this=0xfdf380) at kernel/qeventdispatcher_unix.cpp:621
#15 0x00007fca633b4829 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#16 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:233
#17 0x00007fca5840cc5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fca5840cf48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fca5840cffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fca633b514d in QEventDispatcherGlib::processEvents (this=0xf84af0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#21 0x00007fca61b6f056 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fca63384801 in QEventLoop::processEvents (this=this@entry=0x7fffaf7f63f0, flags=...) at kernel/qeventloop.cpp:149
#23 0x00007fca63384b65 in QEventLoop::exec (this=this@entry=0x7fffaf7f63f0, flags=...) at kernel/qeventloop.cpp:204
#24 0x00007fca6338a5c7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1227
#25 0x00007fca639d75cc in Akonadi::AgentBase::init(Akonadi::AgentBase*) () from /usr/lib/libakonadi-kde.so.4
#26 0x0000000000418e7e in ?? ()
#27 0x00007fca6105bb45 in __libc_start_main (main=0x40bc80, argc=3, argv=0x7fffaf7f6588, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffaf7f6578) at libc-start.c:287
#28 0x000000000040bcae in _start ()

Possible duplicates by query: bug 339395, bug 339328, bug 339209, bug 339046, bug 339024.

Report to https://bugs.kde.org/

Reproducible: Sometimes
Comment 1 Denis Kurz 2017-06-23 20:05:27 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:53:01 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.