Bug 413420 - KRunner does not capture first few characters typed in desktop the first time on new session
Summary: KRunner does not capture first few characters typed in desktop the first time...
Status: RESOLVED DUPLICATE of bug 416145
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.17.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
: 413681 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-10-25 06:07 UTC by HM
Modified: 2020-03-27 16:26 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description HM 2019-10-25 06:07:52 UTC 
SUMMARY
KRunner fails to capture first few characters typed in to the desktop for the first time on a new session. Depending on how fast its typed, KRunner misses the first 1 or 2 characters. This buggy behavior has been present on Wayland for a while now. After updating to Plasma 5.17 this behavior is now experienced on X session.

STEPS TO REPRODUCE
1. Login to new Plasma session
2. Type in command/program name/etc

OBSERVED RESULT
Krunner does not get the first one or two characters of the input. For example 
if you type in "reboot" KRunner gets only "eboot"

EXPECTED RESULT
The whole input starting with the first character at the desktop should be captured as input by KRunner.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux 5.3.7-arch1-1-ARCH x86_64
KDE Plasma Version: 5.17.1
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1
Comment 1 Antonio Rojas 2019-10-31 17:53:12 UTC 
*** Bug 413681 has been marked as a duplicate of this bug. ***
Comment 3 Valdas 2019-11-04 13:40:16 UTC 
This happens sometimes when desktop is empty in 5.17.2 during all session.
Comment 4 HM 2019-11-10 07:00:55 UTC 
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)
Comment 5 David Edmundson 2020-03-27 16:17:53 UTC 
See D26718 which is accepted but not merged.
Comment 6 David Edmundson 2020-03-27 16:26:44 UTC 

*** This bug has been marked as a duplicate of bug 416145 ***