Bug 344749

Summary:	Krunner won't open
Product:	[Plasma] krunner	Reporter:	Alexander Nestorov <alexandernst>
Component:	general	Assignee:	Kai Uwe Broulik <kde>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alexander.lohnau, alexandernst, bjoern, bshah
Priority:	NOR
Version First Reported In:	5.2.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Alexander Nestorov 2015-03-02 14:41:36 UTC

Sometimes, randomly based on each session*, krunner won't run (read as: it won't show up no matter no many times I hit Alt + F2 or Alt + Space). The currently focused application loses the focus, but Krunner doesn't appear.

If I try to start krunner from a console, I get this error: "QCoreApplication::postEvent: Unexpected null receiver"

strace: https://paste.kde.org/pqaeieuyc

*session = is what I consider the time from a boot too a shutdown. In this particular case, this bug either happens 100% of the times in a session, or doesn't happen at all.

If I get to a session of the type that reproduces this bug 100% of the time, the only workaround is rebooting.

Reproducible: Sometimes

Comment 1 Bhushan Shah 2015-03-02 16:57:02 UTC

can you verify that when this happens kglobalaccel5 is not running?

Comment 2 Alexander Nestorov 2015-03-02 18:26:14 UTC

kglobalaccel5 is running when this bug happens. Should I kill kglobalaccel5 ?

Comment 3 Bhushan Shah 2015-03-03 03:20:12 UTC

No, kglobalaccel5 should be running for krunner shortcuts to work, I was trying to find if kglobalaccel is not running and you are not able to use shortcuts is case. anyway, I can not reproduce this bug.

Comment 4 Alexander Nestorov 2015-03-25 13:19:20 UTC

strace output with 5.2.2: https://paste.kde.org/pomgn0lug

Comment 5 Björn Ruberg 2015-10-18 11:11:49 UTC

For me this (still) happens very often.

Comment 6 Alexander Lohnau 2020-10-11 09:51:36 UTC

Now KRunner gets D-Bus activated and not autostarted anymore.