Bug 463857

Summary:	Krunner hangs for 10--20 seconds before opening and freezing desktop
Product:	[Plasma] krunner	Reporter:	Jarno van der Kolk <jarno>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	minor	CC:	alexander.lohnau, nate
Priority:	NOR
Version First Reported In:	5.26.4
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jarno van der Kolk 2023-01-05 00:46:20 UTC

SUMMARY
When starting krunner using Alt+F2 it takes between 10 and 20 seconds before it displays. In the meantime, the desktop is unresponsive. That is, I can't click on anything nor move windows or type.

STEPS TO REPRODUCE
1. Press Alt+F2

OBSERVED RESULT
Krunner opens after a fairly long delay while freezing the desktop.

EXPECTED RESULT
Krunner should open immediately.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 6.1.1-1-Manjaro on X11 using AMD 5700XT
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION
Some info shows up while monitoring "journalctl -f". This message appears first:
Jan 04 19:28:18 goat krunner[2574]: QCommandLineParser: argument list cannot be empty, it should contain at least the executable name

Then after freezing is over, it shows:
Jan 04 19:28:44 goat kwin_x11[1523]: Could not get Interfaces. "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

This only happens on one of my user sessions. Other user sessions on the same machine do not have this issue. This issue also happens when I disable all of the plugins for Krunner.

I also tried balooctl purge in case it had something to do with file searching, but that didn't have an effect.

I can very likely fix this by purging my KDE config, but I'm keeping it for now in case you want me to test things.

Comment 1 Nate Graham 2023-01-09 20:38:40 UTC

Sounds like a broken DBus environment to me.

Comment 2 Jarno van der Kolk 2023-01-20 21:37:35 UTC

I spent a while trying to figure out which one the broken DBus service was but couldn't pin it down. I ended up clearing my .config and .local and that resolved the issue.

I guess it's not clear if having a broken DBus environment should hang the entire desktop like that, but feel free to close if that's expected.

Comment 3 Nate Graham 2023-01-20 21:48:05 UTC

Indeed, having a broken DBus environment will make basically nothing work properly. We rely on this in a lot of ways.