SUMMARY https://bugs.kde.org/show_bug.cgi?id=409499 was closed, but reported issue is not fixed so as requested I created new issue with same problem. SUMMARY When I use krunner and search for certain string, empty / null item is among results. It is always reproducible on one of my computers, but others work fine. Sometimes this empty item is image, sometimes folder, sometimes video. However it is consistent with search strings. Eg. when I search for "spo", it is always image. When I search for "a", it is always archive, when I search for "b" it is always video. If I disable plugin "Desktop Search", empty items do not appear in results. When I click empty item, I get error Malformed URL. I understand this is weird issue. Is there anything I could use to add more detailed information? Can I somehow call krunner query from console? STEPS TO REPRODUCE 1. Open krunner (I have Win key to open krunner) 2. Search for string spo OBSERVED RESULT Empty item appears. See attachment in bug 409499. EXPECTED RESULT No empty item. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
Created attachment 134409 [details] empty result manjaro color theme is not exactly great...
I can reproduce it on different computer. Most of the time I search for, there is always empty image result. Plasma 5.20.4, KF 5.77.0, Qt 5.12.2.
I can reproduce the bug on only one computer with an old install (running KDE neon 5.23.1, KDE Frameworks 5.87.0, Qt 5.15.3, Kernel 5.11.0-38-generic), but not on my other one with a fresh one (running KDE manjaro 5.22.5, KDE Frameworks 5.87.0, Qt 5.15.2, Kernel 5.14.10-1-MANJARO). Both have desktop search enabled in Krunner settings. As reported above, disabling this option removes the empty file from the results, and the file type changes with each search. I noticed the empty file appears only when I type more than 2 characters, and disappears when I type around 6 to 10 characters (this number varies). I would say this bug has been around for more than two years, if not more (been so long I got used to it). But as explained in https://bugs.kde.org/show_bug.cgi?id=430891, running `balooctl purge` and then rebooting fixed the issue. Would be nice to fix it with an update tho, as not everyone will know to do this.