Baloo not indexing, no index file

Ask Fedora
1

Hi,
The questions was asked in the KDE forum (File indexing broken system-wide - Baloo Index could not be opened - Help - KDE Discuss), but it’s suggested that it could be a Fedora-specific problem (it apparently doesn’t happen in Arch with KDE).
The problem is that Baloo doesn’t index. In de settings, indexing is enabled, but it stays inactive.
afbeelding

In the terminal:

balooctl6 status
Baloo Index could not be opened

This work-around doesn’t help:

~ balooctl6 disable      
Disabling and stopping the File Indexer
~ balooctl6 purge  
Deleted the index database
~ balooctl6 enable
Enabling and starting the File Indexer

In the activity monitor, you can’t see any indexing activity.

afbeelding
afbeelding666×904 95.3 KB

2

Have you tried checking Baloo’s permissions yet?

Follow these commands to see if everything is ok

  • Check Baloo Directory Permissions:The Baloo index is usually stored in ~/.local/share/baloo. Make sure the directory has the correct permissions:

bash

ls -ld ~/.local/share/baloo

If permissions are incorrect, you can reset them:

bash

chmod -R 700 ~/.local/share/baloo
  • Remove Existing Database (If Necessary):If the database is corrupted, you might need to remove it manually. This will force Baloo to create a new database.

bash

rm -rf ~/.local/share/baloo
3

Thank you, Nathan.
I didn’t mention, but inside the baloo directory is nothing. Another user tried creating the index file manually, but that didn’t help either.

$ chmod -R 700 ~/.local/share/baloo
$ balooctl6 disable
Disabling and stopping the File Indexer
$ balooctl6 enable
Enabling and starting the File Indexer
$ balooctl6 status
Baloo Index could not be opened

Edit:
Don’t know if this helps, but if you do a check, baloo says it starts checking (but it doesn’t work either, I guess):

$ balooctl6 check
Started search for unindexed files
4

Could you activate the Baloo logs in this way?

To get more detailed logs about what Baloo is doing, you can increase the verbosity of its output:

  1. Enable Debug Logging: You can enable debug logging for Baloo by setting the environment variable for debugging:

bash

export QT_LOGGING_RULES='*.debug=true'
  1. Run Baloo Manually: After setting the logging rule, try running Baloo manually to see more detailed output:

bash

balooctl6 check

This might give you more insight into why the indexing isn’t proceeding as expected.

5

I’m sorry, that doesn’t seem to enable more detailed information:

$ export QT_LOGGING_RULES='*.debug=true'
$ balooctl6 check
Started search for unindexed files
$ balooctl6 disable
Disabling and stopping the File Indexer
$ balooctl6 enable
Enabling and starting the File Indexer
$ balooctl6 check
Started search for unindexed files
6

Could you create a new user and check if Baloo works in that case?

7

Hey Y.Z.,
Thank you for your advice. I don’t feel like making a new user that I will not use. I’ll survive with Catfish and sooner or later an update will fix this I hope…
Or maybe a different solution.

8

I have reported this bug on the KDE bugzilla, and while it wasn’t a solution, it has given me a lead. They asked me to create the file “~/.config/QtProject/qtlogging.ini” and add the following:

[Rules]
kf.baloo=true
kf.baloo.*=true

Then they asked me to run systemctl --user start kde-baloo.service. I did that, and:

$ systemctl --user start kde-baloo.service
Failed to start kde-baloo.service: Unit kde-baloo.service not found

Yeah, the service doesn’t exist, apparently.

Well, actually it does, but under the name plasma-baloorunner.service. Running plasma-baloorunner.service and then listing its status using systemctl --user status plasmabaloorunner.service shows this output:

● plasma-baloorunner.service - KRunner provider for baloo file indexer
     Loaded: loaded (/usr/lib/systemd/user/plasma-baloorunner.service; static)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Fri 2024-08-30 14:04:35 PDT; 11min ago
   Main PID: 16030 (baloorunner)
      Tasks: 6 (limit: 18781)
     Memory: 20.1M (peak: 20.8M)
        CPU: 245ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-baloorunner.service
             └─16030 /usr/libexec/baloorunner

Aug 30 14:04:35 Shlambak systemd[11420]: Starting plasma-baloorunner.service - KRunner provider for baloo file indexer...
Aug 30 14:04:35 Shlambak systemd[11420]: Started plasma-baloorunner.service - KRunner provider for baloo file indexer.
Aug 30 14:04:36 Shlambak baloorunner[16030]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched
Aug 30 14:04:36 Shlambak baloorunner[16030]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched
Aug 30 14:04:36 Shlambak baloorunner[16030]: qt.dbus.integration: Could not find slot Krunner1Adaptor::Teardown

It appears this is some sort of issue with the D-Bus system. I’m not sure what this means, or if the service being under a different name is causing this, but it is a very good lead.