Bug 358587

Summary:	KDE Kontact died unexpectedly
Product:	[Applications] kontact	Reporter:	martin.strecker
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kdenis
Priority:	NOR	Keywords:	drkonqi
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description martin.strecker 2016-01-26 12:46:01 UTC

Application: kontact (4.14.10)
KDE Platform Version: 4.14.10
Qt Version: 4.8.6
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

The crash occurred even though I did not interact with Kontact in any way: I was writing a mail in Thunderbird, and the Kontact window was closed. I have observed a similar behaviour 2 or 3 times before, but it is not frequent.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f91e0319800 (LWP 4509))]

Thread 4 (Thread 0x7f91c2536700 (LWP 4510)):
#0  0x00007f91d786c05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f91dca02eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007f91dca02ee9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x00007f91d78680a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f91dd7f304d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f9181c33700 (LWP 4511)):
#0  0x00007f91d786c05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f91dc775b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007f91dca2aa06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4
#3  0x00007f91d78680a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f91dd7f304d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f9172115700 (LWP 4514)):
[KCrash Handler]
#6  0x00007f91d171ab2e in  () at /lib64/libdbus-1.so.3
#7  0x00007f91d1713bc2 in  () at /lib64/libdbus-1.so.3
#8  0x00007f91d17140d2 in dbus_message_unref () at /lib64/libdbus-1.so.3
#9  0x00007f91da124b09 in QDBusArgument::~QDBusArgument() () at /usr/lib64/libQtDBus.so.4
#10 0x00007f91da10176e in  () at /usr/lib64/libQtDBus.so.4
#11 0x00007f91ddfdd8a3 in  () at /usr/lib64/libQtCore.so.4
#12 0x00007f91da0f0a5c in  () at /usr/lib64/libQtDBus.so.4
#13 0x00007f91da104f7f in QDBusMessage::~QDBusMessage() () at /usr/lib64/libQtDBus.so.4
#14 0x00007f91da101d56 in  () at /usr/lib64/libQtDBus.so.4
#15 0x00007f91ddfbd466 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#16 0x00007f91ddfe77fe in  () at /usr/lib64/libQtCore.so.4
#17 0x00007f91d729bc84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#18 0x00007f91d729bed8 in  () at /usr/lib64/libglib-2.0.so.0
#19 0x00007f91d729bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#20 0x00007f91ddfe6fbe in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#21 0x00007f91ddfb8d4f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#22 0x00007f91ddfb9045 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#23 0x00007f91ddeb64df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#24 0x00007f91ddeb8bbf in  () at /usr/lib64/libQtCore.so.4
#25 0x00007f91d78680a4 in start_thread () at /lib64/libpthread.so.0
#26 0x00007f91dd7f304d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f91e0319800 (LWP 4509)):
#0  0x00007f91dd7e6ced in read () at /lib64/libc.so.6
#1  0x00007f91d72dcb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f91d729b999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f91d729bdf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007f91d729bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#5  0x00007f91ddfe6fde in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007f91dea656a6 in  () at /usr/lib64/libQtGui.so.4
#7  0x00007f91ddfb8d4f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#8  0x00007f91ddfb9045 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#9  0x00007f91ddfbe499 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#10 0x00000000004037f2 in  ()
#11 0x00007f91dd72fb05 in __libc_start_main () at /lib64/libc.so.6
#12 0x0000000000403c97 in _start ()

Reported using DrKonqi

Comment 1 Denis Kurz 2017-06-23 21:02:35 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based 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:51:01 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.