https://bugs.kde.org/show_bug.cgi?id=505520
--- Comment #3 from Greg Berdan <[email protected]> --- 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. Thanks for the response. I don't think I've ever received a response to a bug report before. 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. Greg Berdan On Sun, Aug 10, 2025, 23:44 <[email protected]> wrote: > https://bugs.kde.org/show_bug.cgi?id=505520 > > [email protected] changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |FIXED > Status|REPORTED |NEEDSINFO > > --- Comment #2 from [email protected] --- > (In reply to Greg Berdan from comment #1) > > Literally doing nothing with Obsidian open. I had been doing some light > > markdown editing. Baloo file extractor failure pops up. Im not extracting > > any files. No barckground updates, nothing that seems as if it would > > actually need a file extractor. Earlier I had updated a couple of > plugins. I > > have both disabled and the error continues. Happens again after > rebooting. > > Error returns after seecting restart of Baloo. > > It's quite possible that Baloo is indexing the working file, you edit it, > it > gets changed on disk, Baloo indexes it. More likely is your are indexing > hidden > files and folders as working files are often hidden. For example, you get a > ".my-file.swp" when editing with vi and Baloo has been configured to ignore > "*.swp". You'd need to check if Obsidian creates working copies of its > files > when editing and what naming scheme it uses. > > (In reply to Greg Berdan from comment #1) > > baloo_file_extractor (5.115.0) using Qt 5.15.13 > > This is now a bit old and there was a fix in April 2024 that caught a lot > of > the database corruption issues. Prior to this there was a slow but steady > stream of reports, after the fix that's more or less stopped. Frameworks > 5.115 > was released February 2024... > > In this instance, your short term fix is to purge the index and reindex > clean > ("balooctl purge" or maybe with "balooctl6", close down Baloo with > "systemctl > stop --user kde-baloo" first) > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
