So, a while ago on my Fedora 40 KDE system, the file indexing stopped working entirely. The settings page just report this:
The “Pause Indexer” button does not work, and disabling and re-enabling File indexing doesn’t do anything.
Running
balooctl6 status
gives the following result:
➜ ~ balooctl6 status
Baloo Index could not be opened
So, after some research I found that others could fix their problem by executing this:
➜ ~ balooctl6 disable
Disabling and stopping the File Indexer
➜ ~ balooctl6 purge
Deleted the index database
➜ ~ balooctl6 enable
Enabling and starting the File Indexer
Which, unfortunately, didn’t fix the issue for me and balooctl6 status
still gave the same message Baloo Index could not be opened
.
What I also noticed was that the index file at ~/.local/share/baloo/index
doesn’t even exist, so when creating it manually using touch .local/share/baloo/index
, an index-lock
file is created automatically, no matter if baloo is enabled or disabled. However, the Baloo Index could not be opened
error persists - both when the index is purged and when it is manually created.
I also tried creating a new user on my system and logging into that user instead to see if it works there, but the exact same issue exists in the newly created account, so it seems to be a system-level issue.
I don’t really know how to obtain proper logs for baloo - running journalctl -b -g baloo
doesn’t give any output, unfortunately, so I really have no idea if I should just do a system reinstall or how to fix the issue and would appreciate any help.