Bug 491966 - Alt+F2 launches unrelated wrong program when typing very fast (e.g. KWin effects KCM instead of KWrite)
Summary: Alt+F2 launches unrelated wrong program when typing very fast (e.g. KWin effe...
Status: RESOLVED DUPLICATE of bug 455239
Alias: None
Product: krunner
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.1.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-21 03:29 UTC by Ellie
Modified: 2025-04-05 18:03 UTC (History)
6 users (show)

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

Attachments
Video of me pressing ALT+F2, typing "kwrite", and pressing enter (89.39 KB, video/webm)
2024-08-21 03:29 UTC, Ellie 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ellie 2024-08-21 03:29:49 UTC 
Created attachment 172798 [details]
Video of me pressing ALT+F2, typing "kwrite", and pressing enter

SUMMARY

Alt+F2 will apparently launch an unrelated wrong program when typing too fast. See attached video where I type "kwrite" into ALT+F2, but the KDE system settings come up.

STEPS TO REPRODUCE

1. Type fast into ALT+F2, "kwrite" seems to reproduce it well

OBSERVED RESULT

Wrong program, e.g. KDE system settings, is launched when I type too fast.

EXPECTED RESULT

Correct program, in this case kwrite, is launched no matter how fast I type.

SOFTWARE/OS VERSIONS

Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: postmarketOS Edge
KDE Plasma Version: 6.1.4
KDE Frameworks Version:  6.5.0
Qt Version:  6.7.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-08-21 03:34:42 UTC 
Can reproduce the issue exactly.
Comment 2 John Kizer 2025-04-05 18:03:07 UTC 
Hi - merging this in with what appears to be the same underlying issue of KRunner results not updating in enough time for quickly-typed searches. Thanks!

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