https://bugs.kde.org/show_bug.cgi?id=505520
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |WAITINGFORINFO --- Comment #4 from [email protected] --- On 11/08/2025 17:05, Greg Berdan wrote: > Already went through the procedure to kill Baloo, because it was instantly > in a failed state right at start up. Used AI to find the solution and > followed the steps to purge and rebuild. Worked perfectly. The shutdown app > purge and rebuild steps should not be such a hidden secret. There was a time that a Baloo "purge and reindex" was treated with the same reverence as "turn it off and on again". I assume it's good news that that advice is disappearing into history :-) > ... Thanks for the > response. I don't think I've ever received a response to a bug report > before ... Yes, we need more people triaging, it is a mix of understanding an app and understanding people when they have trouble with it 8-/ All the same, I'll say "It's part of the service" :-) > One other note, The file I was working on in Obsidian had been > updated the night before by the original author. I migrated the changes he > made and it reorganized a bunch of the sub directories. Nothing in the > Baloo details specifically mentioned Obsidian, but the only times I would > get the alert was after obsidian had been open for a few minutes. You can run "balooctl monitor" (or maybe "balooctl6 monitor"), that will show you what files Baloo is indexing. Renaming folders and moving files should not cause problems but Baloo may slow down if you delete large folders. I don't know whether there might be issues when Baloo (that watches for changes on the filesystem) is indexing a folder that is sync'd (that may also be watching for changes). -- You are receiving this mail because: You are watching all bug changes.
