SUMMARY In the Application Dashboard, searching for "shutdown", "restart" or "sleep" brings up the "Desktop Session" KCM as the top search result instead of the option themselves, so typing said words and pressing enter just brings up System Settings. This seems specific to the Dashboard, since if I try using the default Application Launcher, KRunner or the search in Overview the results are as expected (with the action coming first and the KCM showing up lower down). STEPS TO REPRODUCE 1. Use the Show Alternatives option to replace the default Application Launcher with the Application Dashboard 2. Open the Application Dashboard 3. Search for "shutdown", "restart" or "logout" OBSERVED RESULT The "Desktop Session" KCM appears as the top search result. EXPECTED RESULT The actions "Shut Down", "Restart" and "Log Out" show up as the top search result respectively. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.2-arch1-1 (64-bit) Graphics Platform: Wayland
Can reproduce in Plasma 6 too. The power/session actions from the Powerdevil runner aren't adequately prioritized here.
I confirm the bug with the keywords : - "éteindre" which returns "search éteindre in google". - hibernate", even partially, returns "energy hibernate". - sleep", on the other hand, returns "sleep" and "hibernate". ------------------- Operating System: openSUSE Leap 15.5 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 5.14.21-150500.55.28-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15.4 Gio of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Notebook Product Name: NLx0MU System Version: Not Applicable
Potentially related bug dealing with search results in krunner not respecting priorities https://bugs.kde.org/show_bug.cgi?id=485881 KRunner prioritizes file search results even though it is set to lower priority than applications
*** Bug 491564 has been marked as a duplicate of this bug. ***