https://bugs.kde.org/show_bug.cgi?id=470665
--- Comment #5 from Maximilian Böhm <m...@elbmurf.de> ---
Nearly all my filesystems are btrfs, with Zstd compression.
Yes, content indexing is on.
balooctl monitor just shows "File indexing running, Checking for changed index
entries" (translated).
Yes, it’s happening over and over again after relogons. I’m not rerunning it
manually. I haven't used the purge command yet.
systemctl status --user 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 Tue 2023-06-06 18:40:24 CEST; 22min ago
Process: 1382 ExecCondition=/usr/bin/kde-systemd-start-condition
--condition baloofilerc:Basic Settings:Indexing-Enabl>
Main PID: 1383 (baloo_file)
Tasks: 4 (limit: 38385)
Memory: 512.0M (high: 512.0M available: 0B)
CPU: 9min 34.248s
CGroup:
/user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service
When did this start… I cannot say for certain. I have witnessed it for a longer
time but mainly ignored it. Maybe even years? I’m just fed up with this
situation as of today.
Is there a command to show which file Baloo tries to index?
--
You are receiving this mail because:
You are watching all bug changes.
