Application: akonadi_imap_resource (4.14) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.13.0-37-generic x86_64 Distribution: Linux Mint 17.1 Rebecca -- Information about the crash: - What I was doing when the application crashed: Nothing out of the ordinary. Just browsing on the internet and downloading a torrent via Ktorrent. -- Backtrace: Application: Microsoft Live Hotmail (geokarak82) of type 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 0x7f1ecc5cf7c0 (LWP 2465))] Thread 2 (Thread 0x7f1eb6894700 (LWP 2722)): #0 0x00007f1ec6f2861a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007f1ec6f28979 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f1ec6ee687b in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f1ec6ee6f52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f1ec6ee70ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f1ecbbff7be in QEventDispatcherGlib::processEvents (this=0x7f1ea00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x00007f1ecbbd10af in QEventLoop::processEvents (this=this@entry=0x7f1eb6893e20, flags=...) at kernel/qeventloop.cpp:149 #7 0x00007f1ecbbd13a5 in QEventLoop::exec (this=this@entry=0x7f1eb6893e20, flags=...) at kernel/qeventloop.cpp:204 #8 0x00007f1ecbacdc5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537 #9 0x00007f1ecbad032f in QThreadPrivate::start (arg=0xd4b7b0) at thread/qthread_unix.cpp:349 #10 0x00007f1ec75cb182 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x00007f1ec7f6e47d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f1ecc5cf7c0 (LWP 2465)): [KCrash Handler] #5 0x00007f1ec985a314 in KIMAP::Session::selectedMailBox() const () from /usr/lib/libkimap.so.4 #6 0x0000000000446b1f in RetrieveItemsTask::startRetrievalTasks (this=this@entry=0xbeeb20) at ../../../resources/imap/retrieveitemstask.cpp:150 #7 0x0000000000446e0e in RetrieveItemsTask::doStart (this=0xbeeb20, session=<optimized out>) at ../../../resources/imap/retrieveitemstask.cpp:98 #8 0x000000000043ab13 in ResourceTask::onSessionRequested (this=0xbeeb20, requestId=<optimized out>, session=0xd4a0d0, errorCode=0) at ../../../resources/imap/resourcetask.cpp:119 #9 0x00000000004648b5 in ResourceTask::qt_static_metacall (_o=0x7fffdfa990c0, _c=13934800, _id=-1, _a=0xd8f9a0) at moc_resourcetask.cpp:69 #10 0x00007f1ecbbe687a in QMetaObject::activate (sender=sender@entry=0xcfa010, m=m@entry=0x482160 <SessionPool::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fffdfa99340) at kernel/qobject.cpp:3539 #11 0x0000000000464962 in SessionPool::sessionRequestDone (this=this@entry=0xcfa010, _t1=_t1@entry=80, _t2=_t2@entry=0xd4a0d0, _t3=_t3@entry=0, _t4=...) at moc_sessionpool.cpp:153 #12 0x000000000045086a in SessionPool::processPendingRequests (this=0xcfa010) at ../../../resources/imap/sessionpool.cpp:257 #13 0x0000000000464a2d in SessionPool::qt_static_metacall (_o=0x7fffdfa990c0, _c=13934800, _id=-1, _a=0xd8f9a0) at moc_sessionpool.cpp:92 #14 0x00007f1ecbbeac1e in QObject::event (this=0xcfa010, e=<optimized out>) at kernel/qobject.cpp:1194 #15 0x00007f1ecaf6be2c in QApplicationPrivate::notify_helper (this=this@entry=0xb8d6c0, receiver=receiver@entry=0xcfa010, e=e@entry=0xbfd3c0) at kernel/qapplication.cpp:4567 #16 0x00007f1ecaf724a0 in QApplication::notify (this=0x7fffdfa99ad0, receiver=0xcfa010, e=0xbfd3c0) at kernel/qapplication.cpp:4353 #17 0x00007f1ec90b0cca in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #18 0x00007f1ecbbd24dd in QCoreApplication::notifyInternal (this=0x7fffdfa99ad0, receiver=receiver@entry=0xcfa010, event=event@entry=0xbfd3c0) at kernel/qcoreapplication.cpp:953 #19 0x00007f1ecbbd5b3d in sendEvent (event=0xbfd3c0, receiver=0xcfa010) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #20 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xb4a220) at kernel/qcoreapplication.cpp:1577 #21 0x00007f1ecbbd5fe3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #22 0x00007f1ecbbfff83 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #23 postEventSourceDispatch (s=0xb7be60) at kernel/qeventdispatcher_glib.cpp:287 #24 0x00007f1ec6ee6e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x00007f1ec6ee7048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x00007f1ec6ee70ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f1ecbbff7a1 in QEventDispatcherGlib::processEvents (this=0xb7bdb0, flags=...) at kernel/qeventdispatcher_glib.cpp:434 #28 0x00007f1ecb00dbe6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00007f1ecbbd10af in QEventLoop::processEvents (this=this@entry=0x7fffdfa99a40, flags=...) at kernel/qeventloop.cpp:149 #30 0x00007f1ecbbd13a5 in QEventLoop::exec (this=this@entry=0x7fffdfa99a40, flags=...) at kernel/qeventloop.cpp:204 #31 0x00007f1ecbbd6b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #32 0x00007f1ecc0b3783 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4 #33 0x0000000000418993 in Akonadi::ResourceBase::init<ImapResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/resourcebase.h:193 #34 0x00007f1ec7e95ec5 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #35 0x0000000000418854 in _start () Possible duplicates by query: bug 349904, bug 340794. Reported using DrKonqi
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.
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.