Bug 361160

Summary:	drkonqi crash loop in QInternal::activateCallbacks(QInternal::Callback, void**)
Product:	[Applications] drkonqi	Reporter:	Michał <mcv>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED UPSTREAM
Severity:	grave	CC:	rlk, sitter
Priority:	NOR
Version:	5.6.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Michał 2016-03-29 23:14:28 UTC

I just updated system to get new Qt hoping that it will eliminate never-ending crashes of plasmashell. But it looks like with plasma-5.6.1 and Qt-5.6 every KDE application crashes on exit. It doesn't affect non-KDE apps. DrKonqi gets into infinite crash-report-crash loop.

It may be a bug in Qt - I have no idea, but some Qt apps that aren't KDE-related don't have this problem.

Since I didn't know where to report general bug, I chose drkonqi. If possible, please move it to the right section.

Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f05d2163800 (LWP 1401))]

Thread 2 (Thread 0x7f05b72fd700 (LWP 1403)):
[KCrash Handler]
#5  0x00007f05b688b930 in ?? ()
#6  0x00007f05cdee4b52 in QInternal::activateCallbacks(QInternal::Callback, void**) () from /usr/lib/libQt5Core.so.5
#7  0x00007f05ce0d4495 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#8  0x00007f05ce107f97 in QObjectPrivate::setParent_helper(QObject*) () from /usr/lib/libQt5Core.so.5
#9  0x00007f05ce108558 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#10 0x00007f05ce10d3e9 in QSocketNotifier::~QSocketNotifier() () from /usr/lib/libQt5Core.so.5
#11 0x00007f05cf5401af in ?? () from /usr/lib/libQt5DBus.so.5
#12 0x00007f05cb172583 in _dbus_watch_list_remove_watch () from /usr/lib/libdbus-1.so.3
#13 0x00007f05cb170a1e in ?? () from /usr/lib/libdbus-1.so.3
#14 0x00007f05cb170a99 in ?? () from /usr/lib/libdbus-1.so.3
#15 0x00007f05cb16f85b in ?? () from /usr/lib/libdbus-1.so.3
#16 0x00007f05cb15a422 in ?? () from /usr/lib/libdbus-1.so.3
#17 0x00007f05cf542042 in ?? () from /usr/lib/libQt5DBus.so.5
#18 0x00007f05cf5421d4 in ?? () from /usr/lib/libQt5DBus.so.5
#19 0x00007f05cf5424e9 in ?? () from /usr/lib/libQt5DBus.so.5
#20 0x00007f05cf532b0e in ?? () from /usr/lib/libQt5DBus.so.5
#21 0x00007f05cdf00de8 in ?? () from /usr/lib/libQt5Core.so.5
#22 0x00007f05cb5b2424 in start_thread () from /usr/lib/libpthread.so.0
#23 0x00007f05cd81acbd in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f05d2163800 (LWP 1401)):
#0  0x00007f05cb5b803f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1  0x00007f05cdf01c8b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5
#2  0x00007f05cdf0099e in QThread::wait(unsigned long) () from /usr/lib/libQt5Core.so.5
#3  0x00007f05cf5328c6 in ?? () from /usr/lib/libQt5DBus.so.5
#4  0x00007f05cf532959 in ?? () from /usr/lib/libQt5DBus.so.5
#5  0x00007f05cd768c38 in __run_exit_handlers () from /usr/lib/libc.so.6
#6  0x00007f05cd768c85 in exit () from /usr/lib/libc.so.6
#7  0x00007f05cd753717 in __libc_start_main () from /usr/lib/libc.so.6
#8  0x000000000041d6c9 in _start ()

I'll try to recompile Qt with debug symbols, but I can't promise it'll work since the last time I failed to do this.

Reproducible: Always

Steps to Reproduce:
Quit any KDE application.

Comment 1 Michał 2016-03-31 10:51:09 UTC

I played around a bit, installed older Qt, then reinstalled the newer one and the problem disappeared. So it looks like it was Qt, moreover it could be a problem with my installation it seems.

Please close.

Comment 2 rlk 2016-04-22 15:40:46 UTC

Seeing same problem with openSUSE 42.1 KDE packages (Plasma 5.6.3, Qt5 5.6.0).  Either there's more to it than just an installation problem or the install/upgrade process isn't right, apparently with multiple distributions.

Comment 3 rlk 2016-04-22 15:43:36 UTC

See also bug 361681.

Comment 4 Harald Sitter 2019-07-03 12:47:31 UTC

Looks like a crash that is entirely within Qt, so it is indeed either a packaging problem (e.g. mixing incompatible parts of Qt) or an actual bug in Qt. I'd bet on the former, so best get in touch with your distribution when this happens again with a recent version of drkonqi. If they can confirm that it isn't a binary compatibility problem the crash likely needs taking up with Qt directly.

That being said, from the trace I would suppose only Qt applications that use dbus would be affected, which is probably why this shows up more with KDE apps since they almost always have some dbus use somewhere.

Comment 5 Harald Sitter 2019-07-12 12:17:08 UTC

*** Bug 361681 has been marked as a duplicate of this bug. ***