Bug 491237 - Plasma search plugins ordering not working consistently
Summary: Plasma search plugins ordering not working consistently
Status: RESOLVED DUPLICATE of bug 489866
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) widget (show other bugs)
Version: 6.1.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-03 23:30 UTC by roworu
Modified: 2024-08-04 00:19 UTC (History)
3 users (show)

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


Attachments
how to reproduce the issue (2.23 MB, video/mp4)
2024-08-03 23:30 UTC, roworu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description roworu 2024-08-03 23:30:10 UTC
Created attachment 172262 [details]
how to reproduce the issue

SUMMARY  
I have two plugins: "Windows" and "Applications". "Windows" is set to be ordered first in Plasma search plugins, and "Applications" is second. In the Application launcher, when typing the names of different currently running applications, sometimes the first search section is a currently running window, but other times it is the application launcher itself. I was unable to find a pattern causing this behavior, but it seems the ordering feature is not working correctly.

STEPS TO REPRODUCE  
1. Set the "Windows" search plugin in the "Plasma Search" settings menu to the first place and mark it as "Favorite".
2. Set the "Applications" search plugin to the second place and also mark it as "Favorite".
3. Type the names of different currently running applications in the search.

OBSERVED RESULT  
The order of the search results varies each time.

EXPECTED RESULT  
The first section should always be "Windows" with a list of currently running windows, and the second should be "Applications".

SOFTWARE/OS VERSIONS  
- Linux: Fedora 40  
- KDE Plasma Version 6.1.3  
- KDE Frameworks Version: 6.4.0  
- Qt Version: 6.7.2

ADDITIONAL INFORMATION  
I have attached a video fragment showing how to reproduce the issue, which may make it easier to understand.
Comment 1 cwo 2024-08-04 00:19:12 UTC
Thank you for the bug report! This issue has already been filed; please follow the linked bug report for updates on a fix.

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