Bug 505520

Created attachment 183940 [details]
New crash information added by DrKonqi

baloo_file_extractor (5.115.0) using Qt 5.15.13

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.

-- Backtrace (Reduced):
#6  0x00007c7be93adabf in Baloo::PositionDB::get(QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#7  0x00007c7be93bb627 in Baloo::WriteTransaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x00007c7be93b0ef1 in Baloo::Transaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
[...]
#11 0x00007c7be870624b in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007c7be86d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5

(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)

Created attachment 183954 [details]
attachment-1878597-0.html

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 <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=505520
>
> tagwerk19@innerjoin.org changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |FIXED
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #2 from tagwerk19@innerjoin.org ---
> (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.

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).

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.