When I boot in my plasma session, krunner will hang for 5-7 seconds for the first search. After this initial delay, everything will work fine until I reboot. I have these plugins for krunner : - Applications - System configuration - Shell command - IM Reproducible: Always Steps to Reproduce: 1. Boot into a plasma session 2. Open krunner with shortcut 3. Start typing Actual Results: Krunner hangs for 5-7 seconds Expected Results: Krunner should perform directly
Created attachment 100449 [details] krunner strace at startup Contains a strace obtained with sudo strace -f -r -s 128 -o log.log -p "$(pidof krunner)" strace if from a startup where krunner hanged. Research typed in was spoti
Same issue here with the latest version on ArchLinux as of today (5.7.5). The first time krunner is used after startup, it takes 5-10s to react, and then it works as expected.
(In reply to nico.cys from comment #2) > Same issue here with the latest version on ArchLinux as of today (5.7.5). > The first time krunner is used after startup, it takes 5-10s to react, and > then it works as expected. Ok, I posted about it on the Arch forums and was advised to deactivate the search plugins and to reactivate them one by one to find the culprit. However, when I deactivated all of them and restarted the machine, krunner appeared to respond nearly instantly at the first invoke (~1s lag before text appeared, instant after that), and all the plugins were active somehow. Maybe it cleared some cache somewhere which made the situation OK again ?
Your workaround didn't fix it for me. I noticed however that when typing the first few letters in the search bar, iotop reports a lot of read access.
Since installing Plasma 5.9.0 on my arch install, the bug has disappeared for me. Can anyone confirm?
I've not noticed this issue on krunner on KDE Neon User Edition or openSUSE Tumbleweed. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!