Hi,

I updated my system today for my weekly update schedule and when i booted up, i noticed that my CPU utilization was unusually high on idle and my hard drive utilization was not going below 100%. Upon further investigation using

Code: Select all

iotop

, i discovered that baloo-file-extractor was the culprit. However, even though i tried disabling it through search settings

Code: Select all

balooctl stop

&

Code: Select all

balooctl disable

, it was still running. I checked the status through

Code: Select all

balooctl status

and it returned

Baloo is currently disabled. To enable, please run balooctl enable.

I am genuinely confused as to how this is possible and would appreciate any solution to or explanation for this bug.

Thank you.

I too have had a terrible time with Baloo, on multiple machines as well with various clean installs, on multiple varients of Kubuntu (including a clean install of the latest KDE NEON).

I am going to now spend some time disabling again. I wish it wasn't enabled by default, or at least if it is, that it was a basic version (I believe it tries to index image content and basically do too much), as it appears (from my experience at least) to be tremendously buggy.

I seem to have problems when I install with a pre-existing home. It is annoying though. I have just done a write up on it at http://masonbee.nz. I will repost it here for others,
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The Baloo file indexer is the KDE neon process that creates a database for use in file search. Usually it works just fine but sometimes after a new install using an old home folder it starts briefly locking the computer every minute or so as it uses all the resources. This is very annoying.

Top is the simplest way to see what processes are using all the resources. This can be started by opening up Konsole and then typing,

top

If it turns that it is Baloo (or baloo_file_extr) that is causing the problems the next step is to see what the status of Baloo is. This can be done by entering,

balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Indexed 202836 / 203909 files
Current size of index is 5.98 GiB

As you can see from mine the indexer still hasn’t finished indexing although as the install happened a week ago there appears to be some problem. A possible solution might be to delete the index and let Baloo rebuild it by disabling Baloo with,

balooctl disable

But the problem with that is that the index will have to be rebuilt so if you are after a quick fix it is probably something to do when you have some time to leave the computer to it.

You could also use the command,

balooctl stop

to temporarily stop the indexing process or you can edit the Baloo config file directly in the ~/.config/ directory. It is called baloofilerc.

My recommendation would be that if you keep on having problems with the index, disable it,delete it and then re-enable the the Baloo indexer when you have some time to let the computer sit overnight. The opposite commands to the ones above will work to start it. eg;

balooctl start

or,

balooctl enable

You might also find that you cannot restart Baloo after stopping it as dbus already has another instance. The easiest way to fix this is to restart.