https://bugs.kde.org/show_bug.cgi?id=409499
--- Comment #22 from floppy5.25 <giu...@laseroptimized.com> --- Another me too comment (meaning baloo_file dups core at startup and baloosearch shows empty lines) Some additional troubleshooting: balooctl disable balooctl purge balooctl enable After a while it seems that index is rebuilt correctly and baloosearch results are accurate but it does not survive a reboot. I tried the above but with an additional: balooctl disable _before rebooting_ and the baloosearch results survive the reboot (of course the indexer is not running. As soon as I: balooctl enable the following message appears: 61924499171376643 "/home/username/" renaming "username" to "" where username is my username, and baloosearch goes back to displaying empty lines and crashing. So it seems, and this might be speculation on my part, that a enabling baloo after a reboot corrupts the index. -- You are receiving this mail because: You are watching all bug changes.
