Bug 355131 - Akonadi crashing after startup, reading IMAP mail folders
Summary: Akonadi crashing after startup, reading IMAP mail folders
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: unspecified
Platform: Mint (Ubuntu based) Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-11-10 12:50 UTC by Eggert Ehmke
Modified: 2018-02-01 09:55 UTC (History)
2 users (show)

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 Eggert Ehmke 2015-11-10 12:50:42 UTC
Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-66-generic x86_64
Distribution: Linux Mint 17.2 Rafaela

-- Information about the crash:
- What I was doing when the application crashed:
started kmail after system startup. This happens each time.

- Unusual behavior I noticed:
numerous messages about invalid certificates.

The crash can be reproduced every time.

-- Backtrace:
Application: eggert.ehmke@berlin.de vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc8d49ed7c0 (LWP 4962))]

Thread 2 (Thread 0x7fc8bff67700 (LWP 5190)):
#0  0x00007fc8cf9ba569 in __GI___pthread_mutex_lock (mutex=0x7fc8b8000a60) at ../nptl/pthread_mutex_lock.c:125
#1  0x00007fc8cf30a981 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc8cf2c90d8 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc8d402a7be in QEventDispatcherGlib::processEvents (this=0x7fc8b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007fc8d3ffc0af in QEventLoop::processEvents (this=this@entry=0x7fc8bff66e20, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fc8d3ffc3a5 in QEventLoop::exec (this=this@entry=0x7fc8bff66e20, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fc8d3ef8c5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#7  0x00007fc8d3efb32f in QThreadPrivate::start (arg=0xb92a20) at thread/qthread_unix.cpp:349
#8  0x00007fc8cf9b8182 in start_thread (arg=0x7fc8bff67700) at pthread_create.c:312
#9  0x00007fc8d036247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fc8d49ed7c0 (LWP 4962)):
[KCrash Handler]
#6  QMetaObject::invokeMethod (obj=0x31, member=<optimized out>, type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166
#7  0x00007fc8d1c69f38 in ?? () from /usr/lib/libkimap.so.4
#8  0x00007fc8d4015c1e in QObject::event (this=0xb1a240, e=<optimized out>) at kernel/qobject.cpp:1194
#9  0x00007fc8d3391e2c in QApplicationPrivate::notify_helper (this=this@entry=0x9494f0, receiver=receiver@entry=0xb1a240, e=e@entry=0x7fc8b0011750) at kernel/qapplication.cpp:4567
#10 0x00007fc8d33984a0 in QApplication::notify (this=this@entry=0x7fffb1f7e810, receiver=receiver@entry=0xb1a240, e=e@entry=0x7fc8b0011750) at kernel/qapplication.cpp:4353
#11 0x00007fc8d14b9cca in KApplication::notify (this=0x7fffb1f7e810, receiver=0xb1a240, event=0x7fc8b0011750) at ../../kdeui/kernel/kapplication.cpp:311
#12 0x00007fc8d3ffd4dd in QCoreApplication::notifyInternal (this=0x7fffb1f7e810, receiver=receiver@entry=0xb1a240, event=event@entry=0x7fc8b0011750) at kernel/qcoreapplication.cpp:953
#13 0x00007fc8d4000b3d in sendEvent (event=0x7fc8b0011750, receiver=0xb1a240) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x90c220) at kernel/qcoreapplication.cpp:1577
#15 0x00007fc8d4000fe3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#16 0x00007fc8d402af83 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#17 postEventSourceDispatch (s=0x93d9c0) at kernel/qeventdispatcher_glib.cpp:287
#18 0x00007fc8cf2c8e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fc8cf2c9048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fc8cf2c90ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fc8d402a7be in QEventDispatcherGlib::processEvents (this=0x90d700, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#22 0x00007fc8d3433be6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007fc8d3ffc0af in QEventLoop::processEvents (this=this@entry=0x7fffb1f7e780, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007fc8d3ffc3a5 in QEventLoop::exec (this=this@entry=0x7fffb1f7e780, flags=...) at kernel/qeventloop.cpp:204
#25 0x00007fc8d4001b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#26 0x00007fc8d44e1783 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4
#27 0x0000000000418993 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 354951.

Possible duplicates by query: bug 355118, bug 355112, bug 355111, bug 355096, bug 355061.

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 20:17:17 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 opportunity 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-02-01 09:55:07 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 much more recent), please open a new one unless it already exists. Thank you for all your input.