Application: kmail (4.14.10) KDE Platform Version: 4.14.10 Qt Version: 4.8.7 Operating System: Linux 4.2.1-1-desktop x86_64 Distribution: "openSUSE Tumbleweed (20151002) (x86_64)" -- Information about the crash: Starting kmail as part of kde autostart. Aside from kde deskto pstart no other user based action happening The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6c6a26c940 (LWP 1847))] Thread 4 (Thread 0x7f6c41988700 (LWP 1951)): #0 0x00007f6c5ff4e07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x00007f6c5c326de6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x00007f6c5c326e19 in () at /usr/lib64/libQtWebKit.so.4 #3 0x00007f6c5ff484a4 in start_thread () at /lib64/libpthread.so.0 #4 0x00007f6c674c180d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f6c3bfff700 (LWP 1981)): #0 0x00007f6c5ff4e07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x00007f6c5c0905e9 in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x00007f6c5c34e8f6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x00007f6c5ff484a4 in start_thread () at /lib64/libpthread.so.0 #4 0x00007f6c674c180d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f6c3b7fe700 (LWP 2013)): #0 0x00007f6c5f16cb54 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x00007f6c5f1284b0 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x00007f6c5f128dc3 in () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f6c5f128f9c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x00007f6c68b9626e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #5 0x00007f6c68b663e1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #6 0x00007f6c68b666f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #7 0x00007f6c68a5fa59 in QThread::exec() () at /usr/lib64/libQtCore.so.4 #8 0x00007f6c68a6223c in () at /usr/lib64/libQtCore.so.4 #9 0x00007f6c5ff484a4 in start_thread () at /lib64/libpthread.so.0 #10 0x00007f6c674c180d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f6c6a26c940 (LWP 1847)): [KCrash Handler] #6 0x00007f6c6740c7a8 in raise () at /lib64/libc.so.6 #7 0x00007f6c6740dbfa in abort () at /lib64/libc.so.6 #8 0x00007f6c564ce8e4 in () at /lib64/libdbus-1.so.3 #9 0x00007f6c564c54a1 in () at /lib64/libdbus-1.so.3 #10 0x00007f6c564b6bd3 in dbus_message_new_method_call () at /lib64/libdbus-1.so.3 #11 0x00007f6c61abe238 in () at /usr/lib64/libQtDBus.so.4 #12 0x00007f6c61ab9982 in () at /usr/lib64/libQtDBus.so.4 #13 0x00007f6c61abbb3b in () at /usr/lib64/libQtDBus.so.4 #14 0x00007f6c61ac86c3 in () at /usr/lib64/libQtDBus.so.4 #15 0x00007f6c61ac8805 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () at /usr/lib64/libQtDBus.so.4 #16 0x00007f6c648ac763 in PimCommon::ImapResourceCapabilitiesManager::searchCapabilities(QString const&) () at /usr/lib64/libpimcommon.so.4 #17 0x00007f6c648ad00c in PimCommon::ImapResourceCapabilitiesManager::slotInstanceAdded(Akonadi::AgentInstance const&) () at /usr/lib64/libpimcommon.so.4 #18 0x00007f6c68b7af60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #19 0x00007f6c63764705 in Akonadi::AgentManager::instanceAdded(Akonadi::AgentInstance const&) () at /usr/lib64/libakonadi-kde.so.4 #20 0x00007f6c63768b16 in () at /usr/lib64/libakonadi-kde.so.4 #21 0x00007f6c63768f84 in () at /usr/lib64/libakonadi-kde.so.4 #22 0x00007f6c68b7af60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #23 0x00007f6c61af232f in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () at /usr/lib64/libQtDBus.so.4 #24 0x00007f6c61af235f in () at /usr/lib64/libQtDBus.so.4 #25 0x00007f6c61af30e7 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/libQtDBus.so.4 #26 0x00007f6c61ab41d5 in () at /usr/lib64/libQtDBus.so.4 #27 0x00007f6c68b80aa1 in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #28 0x00007f6c67eedf1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #29 0x00007f6c67ef49ec in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #30 0x00007f6c695eb63a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #31 0x00007f6c68b67a1d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #32 0x00007f6c68b6ae4e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #33 0x00007f6c68b960de in () at /usr/lib64/libQtCore.so.4 #34 0x00007f6c5f128cc7 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #35 0x00007f6c5f128ef8 in () at /usr/lib64/libglib-2.0.so.0 #36 0x00007f6c5f128f9c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #37 0x00007f6c68b9624e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #38 0x00007f6c67f91946 in () at /usr/lib64/libQtGui.so.4 #39 0x00007f6c68b663e1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #40 0x00007f6c68b666f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #41 0x00007f6c68b6bef9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #42 0x00000000004030ab in () #43 0x00007f6c673f9610 in __libc_start_main () at /lib64/libc.so.6 #44 0x0000000000403879 in _start () 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 more recent), please open a new one unless it already exists. Thank you for all your input.