Bug 485881

Summary:	KRunner prioritizes file search results even though it is set to lower priority than applications
Product:	[Plasma] krunner	Reporter:	Ilya Bizyaev <bizyaev>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	CONFIRMED ---
Severity:	normal	CC:	alexander.lohnau, fanzhuyifan, junkblocker, kdedev, natalie_clarius, nate, pkrauzer94
Priority:	NOR
Version:	6.1.0
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=474981
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ilya Bizyaev 2024-04-21 09:43:56 UTC

SUMMARY
I have KRunner configured with the following modules as favorites, in this order: “KWin”, “Applications”, “Recent files”, “File Search”.
But when I search for “chrome”, it shows all the “Folders”, then “Text documents”, then “Documents”, then “Images”, then “Audio”, then “Files”, then “Archives”, and only then Google Chrome in “Applications”.
Also, when I search for “kwin”, “Launch KWin debug console” is similarly buried under all the file results.

STEPS TO REPRODUCE
1. Configure KRunner as specified above.
2. Do a search for “chrome” or “kwin”.

OBSERVED RESULT
I have to scroll through multiple pages of results before I get to what I need most often.

EXPECTED RESULT
I can just press Enter to launch what I need.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240418
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.6-1-default (64-bit)
Graphics Platform: Wayland 

ADDITIONAL INFORMATION

Comment 1 fanzhuyifan 2024-04-21 16:16:41 UTC

The minimal reproduction example only needs setting filesearch and applications to favorites, and dragging applications before file search. However, file search results are still shown in front.

Comment 2 junkblocker 2024-06-15 04:11:37 UTC

I see even worse behavior. Applications are shown at the end and System Settings are always preferred no matter what.

Comment 3 TraceyC 2024-06-27 23:12:12 UTC

*** Bug 488856 has been marked as a duplicate of this bug. ***