krunner: run it from Konsole hits SIGSEGV (core dump)

[LionNatsu]

Its GUI(maybe a fork) works at the same time perfectly but itself breaks.

lion@Lion-Laptop [ ~ ] $ krunner 
段错误 (核心已转储)
lion@Lion-Laptop [ ~ ] ! 

[LionNatsu]

The first krunner runs as a daemon, and other krunner notify it to show a input box then exit. The question is why they don't exit (normally) but crash.

[MingcongBai]

That's interesting...

[MingcongBai]

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

[MingcongBai]

Upstream bug reported at: https://bugs.kde.org/show_bug.cgi?id=371505.

[MingcongBai]

This issue still exists with Plasma 5.8.2.

[liushuyu]

I think more like a bug of Qt, and need a debug build of Qt to figure it out, since Musescore has the exactly the same problem:

Thread 3 "QDBusConnection" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd657f700 (LWP 6944)]
0x00007ffff0d1a9cf in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5
(gdb) bt
#0  0x00007ffff0d1a9cf in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () at /usr/lib/libQt5Core.so.5
#1  0x00007fffe1e8e530 in  () at /usr/lib/libQt5DBus.so.5
#2  0x00007fffe1e7af62 in  () at /usr/lib/libQt5DBus.so.5
#3  0x00007ffff0b10d78 in  () at /usr/lib/libQt5Core.so.5
#4  0x00007ffff5e4d454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x00007ffff020f7df in clone () at /usr/lib/libc.so.6
(gdb) _

[LionNatsu]

@liushuyu What does it mean? Ummm... Tries to disconnect a closed connection? Or a null connection?

[MingcongBai]

Is this issue still here? @LionNatsu

[liushuyu]

Seems like this problem is resolved in later Qt 5 builds. Please confirm.

[MingcongBai]

Probably resolved since it can no longer be reproduced (obviously...). Closing.