Problem with baloo file extractor

MarioR

Hello everyone.
After a normal system upgrade gone well, at the next restart I noticed that the cpu was running on and on without a particular reason. I open Ksysguard and I found that there was the baloo file extractor trying to open baloo file without result. This is repeating at every boot. So I have to terminate the baloo file by ksysguard to stop the process.
How can I resolve this problem?

brent

To me this is absolutely, painfully normal if you installed something on Budgie you should not have, like a non-default file manager. Tear out the offending package, delete every trace of Baloo, and you are good to go.
Again---I'm speaking on the assumption you are on Budgie. Baloo and Budgie don't work together in my experience.

MarioR

brent no, i'm on plasma and deleting baloo it's not a good idea...

brent

Then I don''t know. Hang in there, though.

Girtablulu

did you add massive amount of new files? because normally this means it's indexing.

you can run balooctl monitor

KDE help guide reg debuging https://community.kde.org/Baloo/Debugging

MarioR

I let it work running the command you said, it index the new file and all the cache of browser, mail client ecc. Half an hour has passed and it has not yet ended... it's not sustainable

Girtablulu

MarioR depending your system this may take a while

but you can exclute specific paths inside the systemsettings, so baloo doesn't index them or disable baloo with balooctl disable but be aware search won't work anymore

MarioR

Girtablulu you can exclute specific paths inside the systemsettings

where do I find this specification?

Girtablulu

MarioR a guide is here https://community.kde.org/Baloo/Configuration or under search

MarioR

for now I disabled it with

 [Basic Settings]
   Indexing-Enabled=false

but if I do ALT+space I still can search.
Thank you.