https://bugs.kde.org/show_bug.cgi?id=446071
--- Comment #12 from tagwer...@innerjoin.org ---
(In reply to dietervdwes from comment #11)
> System continually seems to run the baloo_file_extractor, quite frustrating
> so I've just suspended it.
Do you see it indexing? If you run:
balooctl monitor
does it report files being indexed? Should happen in batches of 40.
Could you be running BTRFS? There is a bug where BTRFS discs were mounted with
"varying" device numbers, the device number wasn't stable reboot to reboot.
Baloo uses a combination of the device number and inode for an internal "ID"
for indexed files, if it sees a file "reappear" with a different ID, it thinks
it's a new file and it should be indexed again. This caught OpenSUSE people a
lot and then Fedora a little. There's a patch on the way.
Final thing to try, as mentioned in comment 9, is to run:
systemctl status --user kde-baloo.service
and see if the Memory (RAM) is being constrained to 512M. This can slow down
indexing to a crawl, particularly when baloo starts to swap. There's a
balancing act here, I've changed my MemoryHigh to 50% (and MemorySwapMax to 0)
with
systemctl edit --user kde-baloo.service
--
You are receiving this mail because:
You are watching all bug changes.
