I don’t understand why Baloo is such a problem for many people. Quite apart from the sense, if it has come to rest again after the initial indexing, I no longer notice anything about it. Well, I could also disable it, but it does not bother me in any way. And that, although I have my data on a slow 6 TB HDD with only 5400 rpm. System is on SSD though.
You’re lucky, it’s not my case. 95% it behaves well. After today’s update, it locked 97% of CPU and RAM for over an hour. It’s ridiculous especially when so many people have such recurring problems with it.
I need to find where it hides first. If I start with baloo again, I can kiss my computer goodbye for an hour or so. Or I could let it run all night long.
If you deleted the index, you probably don’t want to set first run=false
The initial index will take some time but it might not be as bad as before because it is only indexing file names, not the entire contents of the file.
~ is your home directory. So there should be a .config in your home directory.
Umm…if you didn’t make the change in baloofilerc, there is no reason to let it run. 34 hours isn’t really a long time if you have a lot of files. It has to read and index every word of every file.
That is why you make that change in baloofilerc, so it only indexes file names.
After you make that change to the file, you should suspend and purge. After making sure it is really stopped(which may take a few minutes) then start it again. Now it should be go much faster since it is only indexing file names. You should be able to see this with balooctl monitor
Thanks. I’m letting run its course, however long it does. Then I’ll look for the config file. can’t find it now for some reason. After that, I’ll follow your instructions.
I really appreciate your help. I went on the wikis but didn’t find the answer.