Created attachment 134360 [details] Kickoff bug + resulting error prompt SUMMARY Since the last update (roughly early december) typing even a single letter in Kickoff's search field results in a zombie entry being displayed at the end of the search results. STEPS TO REPRODUCE 1. Have KDE Neon updated to the latest version 2. Have Kickoff set as the default launcher 3. Launch Kickoff and type an arbitrary search string (even a single letter will do) OBSERVED RESULT The list of matching results displayed by Kickoff is trailed by a single zombie entry (grey icon, no name, clicking on it results in an error EXPECTED RESULT No zombie entry displayed at all SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-58-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 7.1 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 ADDITIONAL INFORMATION This was tested on three separate machines (two laptops and a NUC), all running KDE Neon 5.20
Do you see the same thing if you perform the same search in KRunner itself, rather than in Kickoff?
(In reply to Nate Graham from comment #1) > Do you see the same thing if you perform the same search in KRunner itself, > rather than in Kickoff? Yes, I just did a random search using KRunner and the zombie entry was there. Interestingly enough, KRunner listed the zombie entry under different MIME types depending on the letter I typed. Letters A,B and C caused KRunner to list the zombie entry as an image, while typing the letter D magically turned it into a spreadsheet. As far as I can tell, these are the three possible options: - image - spreadsheet - document (whatever that means)
Thanks! Seems like an issue in the KRunner baloo runner, then.
(In reply to Nate Graham from comment #3) > Thanks! Seems like an issue in the KRunner baloo runner, then. Can't it be related to this? https://bugs.kde.org/show_bug.cgi?id=430273#c13 It seems it was solved for 5.78 I can only confirm the same bug for me with frameworks 5.77 Temporary workaround: 1. balooctl disable 2. balooctl purge 3. reboot 4. balooctl enable It will crash again at every reboot though
Baloo 5.78 seems to fix the problem
Confirmed, no more blank entry for me either with Baloo 5.78. Let's close this and re-open if anyone else still sees it with Baloo 5.78 or later.
Created attachment 134882 [details] Baloo 5.78 displaying wrong entry upon search
(In reply to Nate Graham from comment #6) > Confirmed, no more blank entry for me either with Baloo 5.78. Let's close > this and re-open if anyone else still sees it with Baloo 5.78 or later. This is not fixed for me, see the latest attached screenshot
*groan* Quick question: does it get fixed if you do a `balooctl purge` to force it to re-index everything, and then reboot the system?
(In reply to Nate Graham from comment #9) > *groan* > > Quick question: does it get fixed if you do a `balooctl purge` to force it > to re-index everything, and then reboot the system? That fixed the problem, thanks!
*** Bug 435594 has been marked as a duplicate of this bug. ***