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: KMail crash on start of day loading into kde 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 0x7f0ab09bf940 (LWP 1812))] Thread 4 (Thread 0x7f0a83fff700 (LWP 1897)): #0 0x00007f0aa66a107f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x00007f0aa2a79de6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x00007f0aa2a79e19 in () at /usr/lib64/libQtWebKit.so.4 #3 0x00007f0aa669b4a4 in start_thread () at /lib64/libpthread.so.0 #4 0x00007f0aadc1480d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f0a82e6e700 (LWP 1898)): #0 0x00007f0aa66a107f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x00007f0aa27e35e9 in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x00007f0aa2aa18f6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x00007f0aa669b4a4 in start_thread () at /lib64/libpthread.so.0 #4 0x00007f0aadc1480d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f0a81fb1700 (LWP 1899)): #0 0x00007f0aadc0be7d in poll () at /lib64/libc.so.6 #1 0x00007f0aa587be94 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007f0aa587bf9c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f0aaf2e926e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #4 0x00007f0aaf2b93e1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #5 0x00007f0aaf2b96f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #6 0x00007f0aaf1b2a59 in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x00007f0aaf1b523c in () at /usr/lib64/libQtCore.so.4 #8 0x00007f0aa669b4a4 in start_thread () at /lib64/libpthread.so.0 #9 0x00007f0aadc1480d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f0ab09bf940 (LWP 1812)): [KCrash Handler] #6 0x00007f0aadb5f7a8 in raise () at /lib64/libc.so.6 #7 0x00007f0aadb60bfa in abort () at /lib64/libc.so.6 #8 0x00007f0a9cc218e4 in () at /lib64/libdbus-1.so.3 #9 0x00007f0a9cc184a1 in () at /lib64/libdbus-1.so.3 #10 0x00007f0a9cc09bd3 in dbus_message_new_method_call () at /lib64/libdbus-1.so.3 #11 0x00007f0aa8211238 in () at /usr/lib64/libQtDBus.so.4 #12 0x00007f0aa820c982 in () at /usr/lib64/libQtDBus.so.4 #13 0x00007f0aa820eb3b in () at /usr/lib64/libQtDBus.so.4 #14 0x00007f0aa821b6c3 in () at /usr/lib64/libQtDBus.so.4 #15 0x00007f0aa821b805 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () at /usr/lib64/libQtDBus.so.4 #16 0x00007f0aaafff763 in PimCommon::ImapResourceCapabilitiesManager::searchCapabilities(QString const&) () at /usr/lib64/libpimcommon.so.4 #17 0x00007f0aab00000c in PimCommon::ImapResourceCapabilitiesManager::slotInstanceAdded(Akonadi::AgentInstance const&) () at /usr/lib64/libpimcommon.so.4 #18 0x00007f0aaf2cdf60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #19 0x00007f0aa9eb7705 in Akonadi::AgentManager::instanceAdded(Akonadi::AgentInstance const&) () at /usr/lib64/libakonadi-kde.so.4 #20 0x00007f0aa9ebbb16 in () at /usr/lib64/libakonadi-kde.so.4 #21 0x00007f0aa9ebbf84 in () at /usr/lib64/libakonadi-kde.so.4 #22 0x00007f0aaf2cdf60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #23 0x00007f0aa824532f in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () at /usr/lib64/libQtDBus.so.4 #24 0x00007f0aa824535f in () at /usr/lib64/libQtDBus.so.4 #25 0x00007f0aa82460e7 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/libQtDBus.so.4 #26 0x00007f0aa82071d5 in () at /usr/lib64/libQtDBus.so.4 #27 0x00007f0aaf2d3aa1 in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #28 0x00007f0aae640f1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #29 0x00007f0aae6479ec in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #30 0x00007f0aafd3e63a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #31 0x00007f0aaf2baa1d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #32 0x00007f0aaf2bde4e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #33 0x00007f0aaf2e90de in () at /usr/lib64/libQtCore.so.4 #34 0x00007f0aa587bcc7 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #35 0x00007f0aa587bef8 in () at /usr/lib64/libglib-2.0.so.0 #36 0x00007f0aa587bf9c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #37 0x00007f0aaf2e924e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #38 0x00007f0aae6e4946 in () at /usr/lib64/libQtGui.so.4 #39 0x00007f0aaf2b93e1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #40 0x00007f0aaf2b96f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #41 0x00007f0aaf2beef9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #42 0x00000000004030ab in () #43 0x00007f0aadb4c610 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.