Now, I have bothered the community with my laptop not responsive. On all DE I installed I used to install Dolphin which brings Balloo with it.
I insisted on finding out. I found out over the past 2 days on KDE Plasma:
If Baloo is indexing it is taking most of the CPU
When it finishes indexing (or I stop Baloo) the machine is running perfectly.
I -surprisingly- found out like Baloo “forgets” it has already indexed some files and suddenly come back to index them (again), which makes it unresponsive, then works fine, then “forget”, then re-index…
I have another issue with Baloo/Dolphin, when I search for a file, , a unique single file, it brings in search result several copies of the same file, (opening folder location of all of them actually opens the same folder that has nothing but actually this file only with some folders)
What might be causing Baloo to “forget” and re-index frequently? (is it related to BTRFS/Snapshot, TimeShift snapshots?)
Why is it showing in Dolphin several copies pointing actually to the same file in the same location?
I cannot help with your problems, but I can say to you that Baloo, expecially if you started or are using a DE different then KDE (and with this I intend a new installation not made directly with KDE) tends to do a lot a problem. The only time I hadn’t have any problem with it is when I’ve installed directly KDE from iso/base arch.
I did all, but not purge.
May be as dalto it is related to TimeShift and snapshots?
I believe in brainstorming, as I believ Linux is all about brainstorming to get best results.
Hopefully this can help other users as well as I found some saying almost the same thing.
balooctl purge is not necessary, it just erases the index from your drive. If I’m not using the indexing service, why keep an old index? Its existence is just dead space on the drive, and a potential security vulnerability.
And balooctl status is just to check that it is truly dead.