https://bugs.kde.org/show_bug.cgi?id=472164
Bug ID: 472164
Summary: KRunner should wait for results before starting the
app
Classification: Plasma
Product: krunner
Version: 5.27.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---
SUMMARY
When using the search function in the task manager or when using KRunner, I
open type quite fast and hit enter as soon as I am done typing (and expect the
correct result to show up) even if the search is not fully complete. This often
results in the wrong application from starting.
replicating this exactly is a little difficult because the timing is relatively
precise.
STEPS TO REPRODUCE
1. open task bar search
2. immediately type "fire" (searching for firefox)
3. *immediately* hit enter
OBSERVED RESULT
The files app opens.
You will notice that when you type "fi", the files app is listed at the top
above firefox.
when you finish typing "fire", files will still be at the top for a small
amount of time before firefox becomes the top result (waiting for search to
complete). if you press enter before firefox is at the top, the files app will
open even if the user clearly intended firefox to launch.
this also happens with other applications but this is the one I found to happen
most often.
EXPECTED RESULT
firefox opens instead of files.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 38 (nobara official with x11)
Specs: i7-8750h + gtx1060
ADDITIONAL INFORMATION
This could be fixed by changing krunner so typing a letter will immediately
invalidate all results until the search is complete with the new character.
Then open the result even if the search is complete after the user presses the
enter button.
TLDR: close krunner/taskbar after user presses enter, complete search in the
background, open top result
I hope my explanation makes sense.
--
You are receiving this mail because:
You are watching all bug changes.
