Bug 511314

Summary: Fuzzy search will not prioritize exact matches
Product: [Plasma] krunner Reporter: LGF <cometzeldrake>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: alexander.lohnau, natalie_clarius, nate, thecaptain
Priority: NOR    
Version First Reported In: 6.5.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: searching for GIMP does not show GIMP as the first result

Description LGF 2025-10-29 12:28:23 UTC
Created attachment 186285 [details]
searching for GIMP does not show GIMP as the first result

SUMMARY

The new fuzzy search in Krunner as part of Plasma 6.5 (downloaded from here: https://discussion.fedoraproject.org/t/fedora-kde-early-plasma-6-5-0/169599 ) is great and something I like very much, but it should prioritize exact matches over fuzzy matches.

In this case it is prioritizing LibreOffice Impress, probably because of the "imp" matching, over GIMP itself. This is partly because GIMP is called GNU Image Manipulation Program, but "gimp" is in the Keywords section of the relevant file (/usr/share/applications/gimp.desktop) so it should check for that exact match first.

OBSERVED RESULT

LibreOffice Impress is first in the list.

EXPECTED RESULT

GIMP should be first in the list.

SOFTWARE/OS VERSIONS
Fedora Linux 42
KDE Plasma Version: 6.5.0
KDE Frameworks Version: 6.19.0
Qt Version:  6.9.2

ADDITIONAL INFORMATION

It's relatively straightforward to modify aforementioned gimp.desktop to have GIMP at the front of it in clear and unmissable letters under the Name= field, but it probably shouldn't do this in the first place.

Very similar to https://bugs.kde.org/show_bug.cgi?id=511235 and https://bugs.kde.org/show_bug.cgi?id=511237 , but this is specifically about finding an exact match in the Keywords section of the relevant .desktop file
Comment 1 David Edmundson 2025-10-29 16:10:06 UTC
*** Bug 511319 has been marked as a duplicate of this bug. ***
Comment 2 Nate Graham 2025-10-29 20:31:29 UTC

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