Bug 371505

Summary: KRunner crashes when launched from terminal emulators
Product: [Plasma] krunner Reporter: Jeff Bai <jeffbaichina>
Component: generalAssignee: Kai Uwe Broulik <kde>
Status: RESOLVED WORKSFORME    
Severity: crash CC: alexander.lohnau, jeffbaichina, lion, zhaixiang
Priority: NOR    
Version First Reported In: 5.8.4   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
URL: https://github.com/AOSC-Dev/aosc-os-abbs/issues/479
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jeff Bai 2016-10-23 02:56:43 UTC 
When running Plasma Desktop session (so KRunner is running as a daemon in the background), if one would launch the `krunner' command from any terminal emulator, a KRunner dialog will show up (prompting for input, works as expected), but then crashes.

I did not get the chance to make a full debug build of plasma-workspace to test this issue out thoroughly - but here is the last call until the segmentation fault:

0x00007ffff6570dd7 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5

----------------------------------------------------

(gdb) bt
#0  0x00007ffff62dbdd7 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5
#1  0x00007ffff7391820 in ?? () from /usr/lib/libQt5DBus.so.5
#2  0x00007ffff737e0b5 in ?? () from /usr/lib/libQt5DBus.so.5
#3  0x00007ffff60d1b6f in ?? () from /usr/lib/libQt5Core.so.5
#4  0x00007ffff5075474 in ?? () from /usr/lib/libpthread.so.0
#5  0x00007ffff5932e9f in clone () from /usr/lib/libc.so.6

Reproducible: Always

Steps to Reproduce:
1. Launch a Plasma Desktop session.
2. Open up Konsole, or any terminal emulator.
3. Run the command `krunner' as the current user.
4. Boom.
Comment 1 Jeff Bai 2016-10-23 04:04:25 UTC 
This issue still exists with Plasma 5.8.2.
Comment 2 Leslie Zhai 2016-11-29 03:51:58 UTC 
krunner v5.28.0 reproduced!
Comment 3 Leslie Zhai 2016-11-29 04:28:18 UTC 
/usr/bin/krunner
ASAN:DEADLYSIGNAL
=================================================================
==3706==ERROR: AddressSanitizer: SEGV on unknown address 0x7fb619331368 (pc 0x7fb62feb09cf bp 0x61100003bf00 sp 0x7fb619b33a10 T2)
==3706==The signal is caused by a READ memory access.
    #0 0x7fb62feb09ce in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) (/usr/lib/libQt5Core.so.5+0x2b69ce)
    #1 0x7fb631f8952f  (/usr/lib/libQt5DBus.so.5+0x2952f)
    #2 0x7fb631f75f61  (/usr/lib/libQt5DBus.so.5+0x15f61)
    #3 0x7fb62fca6d77  (/usr/lib/libQt5Core.so.5+0xacd77)
    #4 0x7fb62f358453 in start_thread (/usr/lib/libpthread.so.0+0x7453)
    #5 0x7fb62ea787de in __GI___clone (/usr/lib/libc.so.6+0xe87de)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/usr/lib/libQt5Core.so.5+0x2b69ce) in QObject::disconnect(QObject const*, char const*, QObject const*, char const*)
Thread T2 (QDBusConnection) created by T0 here:
    #0 0x436ccd in __interceptor_pthread_create (/usr/bin/krunner+0x436ccd)
    #1 0x7fb62fca6278 in QThread::start(QThread::Priority) (/usr/lib/libQt5Core.so.5+0xac278)

==3706==ABORTING


so it might be UPSTREAM issue https://bugreports.qt.io/browse/QTBUG-52988