Bug 314603 - Unpredictable sorting/filtering in krunner
Summary: Unpredictable sorting/filtering in krunner
Status: RESOLVED FIXED
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-07 14:59 UTC by Kvaks
Modified: 2015-01-23 16:33 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kvaks 2013-02-07 14:59:29 UTC
I have the following problem with krunner:

When typing the first few characters and seeing my intended target appear, sometimes if I type yet more characters, the target drops down on the list and an item seemingly much less relevant gets promoted to the top.

This is a problem because when typing, my fingers automatically keep typing the word even if the intended target has appeared on top, and then press enter before realizing there suddenly is a new (and undesired) item on top. Result: Wrong item is launched.

Example: I want to launch the System Settings application. I start typing "Sys" and the desired item appears, but I continue to type "te" because of linguistic and muscle memories, and the item is still there, yet when I complete the word with an "m" the top item is suddenly "Synaptic Package Manager". This all happens fast, and in cases like this I often end up launching synaptic instead of System Settings.

It seems to me that continuing to type characters specifically matching the item that is already on top of the list, should not move that item down the list. The current behavior is unpredictable and unintuitive.

Screenshots of the above described behavior: 

"Syste": http://i.imgur.com/g3AlpBt.jpg
"System": http://i.imgur.com/Go9ULrY.jpg
Comment 1 Vishesh Handa 2015-01-23 16:33:20 UTC
The underlying technology in KRunner has changed significantly for Plasma 5. We're fairly certain that upgrading should solve this issue.