Application: kontact (4.14.3) KDE Platform Version: 4.14.3 Qt Version: 4.8.6 Operating System: Linux 3.17.4-1-desktop x86_64 Distribution: "openSUSE 20141208 (Tumbleweed) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I had Kontact active on the desktop and was busy to enter another another bug report in Firefox. So in fact it was something authonomous in Kontact. Only the KMail window was busy. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffd42736800 (LWP 2905))] Thread 4 (Thread 0x7ffd2449c700 (LWP 2906)): #0 0x00007ffd39d5c85f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007ffd3d4ec6f6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x00007ffd3d4ec729 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x00007ffd39d583a4 in start_thread () from /lib64/libpthread.so.0 #4 0x00007ffd3fcc9a4d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7ffce3b99700 (LWP 2907)): #0 0x00007ffd39d5c85f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007ffd3d25eeed in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x00007ffd3d514256 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x00007ffd39d583a4 in start_thread () from /lib64/libpthread.so.0 #4 0x00007ffd3fcc9a4d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7ffcd010c700 (LWP 3019)): [KCrash Handler] #5 0x00007ffd3687db3e in _dbus_counter_notify (counter=0x22bee60) at dbus-resources.c:187 #6 0x00007ffd36876bc2 in free_counter (element=0x22bee60, data=0x2af9660) at dbus-message.c:639 #7 0x00007ffd368770d2 in dbus_message_cache_or_finalize (message=0x2af9660) at dbus-message.c:661 #8 dbus_message_unref (message=0x2af9660) at dbus-message.c:1707 #9 0x00007ffd3f069b09 in q_dbus_message_unref (message=<optimized out>) at qdbus_symbols_p.h:296 #10 ~QDBusArgumentPrivate (this=<optimized out>, __in_chrg=<optimized out>) at qdbusargument.cpp:66 #11 QDBusArgument::~QDBusArgument (this=0x22bee60, __in_chrg=<optimized out>) at qdbusargument.cpp:348 #12 0x00007ffd3f04676e in qMetaTypeDeleteHelper<QDBusArgument> (t=0x2af73e0) at ../../src/corelib/kernel/qmetatype.h:134 #13 0x00007ffd404309d3 in clear (d=0x28061b0) at kernel/qvariant.cpp:290 #14 0x00007ffd3f035a5c in node_destruct (this=<optimized out>, to=<optimized out>, from=<optimized out>) at ../../src/corelib/tools/qlist.h:431 #15 free (this=<optimized out>, data=<optimized out>) at ../../src/corelib/tools/qlist.h:757 #16 QList<QVariant>::~QList (this=0x22bee60, __in_chrg=<optimized out>) at ../../src/corelib/tools/qlist.h:732 #17 0x00007ffd3f049f7f in QDBusMessage::~QDBusMessage (this=0x22bee60, __in_chrg=<optimized out>) at qdbusmessage.cpp:537 #18 0x00007ffd3f046d56 in ~QDBusCallDeliveryEvent (this=0x2a9cb70, __in_chrg=<optimized out>) at qdbusintegrator_p.h:93 #19 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x2a9cb70, __in_chrg=<optimized out>) at qdbusintegrator_p.h:93 #20 0x00007ffd404105b6 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x19cd550) at kernel/qcoreapplication.cpp:1593 #21 0x00007ffd40410a53 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #22 0x00007ffd4043a92e in sendPostedEvents () at kernel/qcoreapplication.h:236 #23 postEventSourceDispatch (s=0x7ffcc80012e0) at kernel/qeventdispatcher_glib.cpp:300 #24 0x00007ffd3978ba04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x00007ffd3978bc48 in ?? () from /usr/lib64/libglib-2.0.so.0 #26 0x00007ffd3978bcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x00007ffd4043a0ee in QEventDispatcherGlib::processEvents (this=0x7ffcc80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:450 #28 0x00007ffd4040be9f in QEventLoop::processEvents (this=this@entry=0x7ffcd010bde0, flags=...) at kernel/qeventloop.cpp:149 #29 0x00007ffd4040c195 in QEventLoop::exec (this=this@entry=0x7ffcd010bde0, flags=...) at kernel/qeventloop.cpp:204 #30 0x00007ffd403090bf in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538 #31 0x00007ffd4030b79f in QThreadPrivate::start (arg=0x1b74070) at thread/qthread_unix.cpp:349 #32 0x00007ffd39d583a4 in start_thread () from /lib64/libpthread.so.0 #33 0x00007ffd3fcc9a4d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ffd42736800 (LWP 2905)): #0 0x00007ffd3fcbd57d in read () from /lib64/libc.so.6 #1 0x00007ffd397cc750 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007ffd3978b714 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x00007ffd3978bb7b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x00007ffd3978bcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x00007ffd4043a10e in QEventDispatcherGlib::processEvents (this=0x17c0fd0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x00007ffd40eb86c6 in ?? () from /usr/lib64/libQtGui.so.4 #7 0x00007ffd4040be9f in QEventLoop::processEvents (this=this@entry=0x7fffeb810360, flags=...) at kernel/qeventloop.cpp:149 #8 0x00007ffd4040c195 in QEventLoop::exec (this=this@entry=0x7fffeb810360, flags=...) at kernel/qeventloop.cpp:204 #9 0x00007ffd404115e9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #10 0x00000000004037f2 in ?? () #11 0x00007ffd3fc06b45 in __libc_start_main () from /lib64/libc.so.6 #12 0x0000000000403c97 in _start () Reported using DrKonqi
This bug has never been confirmed for a Kontact 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.
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.