You are not logged in.
Using KDE Plasma 6 here. I noticed at my last reboot that baloo was taking a lot of time and SSD bandwidth to index files.
I then remembered that I had copied a large directory in my home directory, that I didn't care to index. So I excluded it from indexing.
After that, I ran:
balooctl6 suspend
balooctl6 purge
But the latter command would fail every time with:
Stopping the File Indexer ............................................................................................................................................................................................................................................................................................................... - failed to stop!
I then tried stopping the service manually with:
systemctl --user stop plasma-baloorunner.service
The service stopped. But the '/usr/lib/kf6/baloo_file' process kept running. What a bummer. What's the correct way of handling this? Is this a known issue?
Edit: For the record, I just killed the baloo_file process hoping it wouldn't cause issues. I was going to purge the index anyway. That did allow the 'balooctl6 purge' command to succeed.
From what I've read, baloo looks like a bit of a dog. It hasn't caused me much problems previously, but in hindsight, I think this isn't the first time I noticed that once the indexer was running, it was impossible to stop it, short of killing the corresponding processes. Not very pretty.
Last edited by OpusOne (2024-07-24 06:05:05)
Offline
https://bugs.kde.org/show_bug.cgi?id=487916#c3
pkill baloo_file
pkill -9 baloo_file
The process probably doesn't respond because it's busy watching your porn
Offline
https://bugs.kde.org/show_bug.cgi?id=487916#c3
pkill baloo_file pkill -9 baloo_file
The process probably doesn't respond because it's busy watching your porn
Lol. Our posts crossed. I edited and yes, I killed it. As I said, baloo doesn't look like it's very well uh, written. Or something. Oh well.
Offline