https://bugs.kde.org/show_bug.cgi?id=413420
--- Comment #4 from HM <mcmailf...@protonmail.com> --- I heard from someone that this behavior is because KRunner is now started on demand. I checked and did find that KRunner is now not started at boot. It only gets started once you type in something at the desktop and depending on how fast you type, misses the first few inputs. Isn't this bad design, taking away from the functionality and productivity that KRunner gives letting you just do stuff from the get go. Current buggy behavior can be worked around by starting KRunner at boot - create an autostart entry with command 'krunner -d' (-d for starting in background) -- You are receiving this mail because: You are watching all bug changes.
