Bug 470622 - Krunner runs/starts whatever is currently highlighted when pressing return, but it should finish the search and then run/start
Summary: Krunner runs/starts whatever is currently highlighted when pressing return, b...
Status: CONFIRMED
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Alexander Lohnau
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2023-06-04 08:31 UTC by Julian
Modified: 2023-06-09 19:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julian 2023-06-04 08:31:48 UTC
SUMMARY
I came from Gnome and used Super + Application Name to start apps, it works so nice and is super fast and never started wrong apps for me. However with KRunner i have the problem that i type and hit return so fast that the search for the application name i wan't to start did not even run / finish, so it just starts whatever is currently highlighted (can be results from previous searches or whatever).
Imo if i press enter and the search was not performed / finished with the last input letter before return then perform / wait for the search and start the right thing.


STEPS TO REPRODUCE
1. Use KRunner to search for an app name
2. as soon as you fully typed the app name hit return as fast as possible

OBSERVED RESULT
KRunner starts whatever was highlighted in the search before

EXPECTED RESULT
KRunner should check if the search was completely done with all letters before the return and then doing the run with the correct search result


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 38
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel: 6.3.4-201.fc38.x86_64 (64-bit)

ADDITIONAL INFORMATION
- I have this problem on Kubuntu and Fedora
- Wayland
Comment 1 Alexander Lohnau 2023-06-09 19:13:40 UTC
IMHO waiting for it to finish might be a bad idea, because some runners do network requests. How about having a timeout so that we do not wait longer than lets say 500ms for results to load?