https://bugs.kde.org/show_bug.cgi?id=487916
--- Comment #2 from Sergio <sergio.calleg...@gmail.com> ---
Reeboted to make sure everything is clear. Before the reboot baloo was using 0%
I/O.
Then tried
```
systemctl --user status kde-baloo
● kde-baloo.service - Baloo File Indexer Daemon
Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset:
enabled)
Active: active (running) since Mon 2024-06-03 09:09:49 CEST; 1min 7s ago
Process: 1618 ExecCondition=/usr/bin/kde-systemd-start-condition
--condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited,
status=0/SUCCE>
Main PID: 1629 (baloo_file)
Tasks: 3 (limit: 19061)
Memory: 249.1M (high: 512.0M available: 262.8M peak: 249.2M)
CPU: 2.458s
CGroup:
/user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service
└─1629 /usr/lib/kf6/baloo_file
Jun 03 09:09:49 zagar systemd[1468]: Starting Baloo File Indexer Daemon...
Jun 03 09:09:49 zagar systemd[1468]: Started Baloo File Indexer Daemon.
```
Indeed it is limited to 512MB. Why does it say "disabled", though? If it is
disabled why is it starting and how?
At this point I am over 5 minutes after the boot. `baloo_file` is still hogging
the I/O.
Now about 10 minutes after the boot. `baloo_file` has finally calmed down. In
many occasions it took much more. For these first 10' the machine has been
hardly usable. This was not happening before my distro updated to plasma 6
(maybe bringing many other changes together with that, which may be the actual
cause of what I am observing).
Index file is very small:
```
Total files indexed: 382,267
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 238.11 MiB
```
Home is on rotating HD and btrfs. Probably no one is anymore testing on
rotating HDs, but they are still around.
>From a usability point of view, two aspects are IMHO of concern:
1. `balooctl6 suspend` seems to do nothing at all.
2. `balooctl6 disable` sets baloo to be disabled, but does not stop
`baloo_file` at all.
--
You are receiving this mail because:
You are watching all bug changes.
