Bug 438860

Summary: Search results in Kickoff differ from krunner
Product: [Plasma] plasmashell Reporter: dagobertram
Component: Application Launcher (Kickoff)Assignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: normal CC: alexander.lohnau, mikel5764, nate, plasma-bugs
Priority: NOR    
Version: 5.22.1   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Kickoff and krunner present search results very differently

Description dagobertram 2021-06-18 11:12:08 UTC 
I am not sure if this is intentional but the search results from the new Kickoff menu and krunner differ in a big way. Krunner is much better in sorting and presenting search results than Kickoff.

I would like Kickoff to get the same functionality krunner has (sorting wise) which would be exceptionally useful and a big improvement to Kickoff. Isn't krunner driving the Kickoff search functionality anyway?

In which context is Kickoff right now better/different from krunner except of showing more than just the search bar when activated? Is there even a need to have both? I was always confused why there are two tools doing almost the same stuff in almost the same way.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Kernel Version: 5.4.0-74-generic (64-bit)
Graphics Platform: X11
Processors: 2 × Intel® Pentium® CPU G3440 @ 3.30GHz
Memory: 7,7 GiB of RAM
Graphics Processor: AMD Radeon HD 7800 Series
Comment 1 dagobertram 2021-06-18 11:15:08 UTC 
Created attachment 139480 [details]
Kickoff and krunner present search results very differently
Comment 2 Nate Graham 2021-06-18 13:08:10 UTC 
Yes, this is a known bug. They don't use the same weighting/ordering models, so the results aren't exactly the same. We plan to fix it in KF6 by making the model public so that every KRunner-using UI can access it.

Alexander, do you know if there's an existing bug report for this?
Comment 3 Nate Graham 2021-07-23 16:12:00 UTC 
Lol it's Bug 431204 which I even filed

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