If we open ksysguard and close it, we will see warning message that KDEInit can't run /usr/bin/ksysguard. Whats more if ksysguard is started from krunner, krunner becomes unresponsive, we can interact it after ksysguard is closed. Reproducible: Always Steps to Reproduce: 1. Start ksysgurad (from menu or krunner) 2. Close ksysgurad 3. Warning message shows up Actual Results: Warning message is generated after ksysguard is closed. Expected Results: ksysguard should be temrinated without any warning messages.
grep -i dbus /usr/share/applications/org.kde.ksysguard.desktop X-DBUS-StartupType=Multi X-DBUS-ServiceName=org.kde.ksysguard appears to me that ksysguard claims it registers on dbus, except it doesn't really.
I can confirm the bug, but one can use dbus to launch ksysguard to make it work in this case.
Git commit b3900ddedacc92db2eeec05e521fdaee94076230 by Hrvoje Senjan. Committed on 26/02/2015 at 14:57. Pushed by hrvojes into branch 'Plasma/5.2'. Register KSysguard to DBus Unbreaks starting the app via KRun Reviewed-by: Bhushan Shah M +1 -0 gui/CMakeLists.txt M +5 -1 gui/ksysguard.cpp http://commits.kde.org/ksysguard/b3900ddedacc92db2eeec05e521fdaee94076230
It affect me too, and still the latest update doesn't overcome this bug