https://bugs.kde.org/show_bug.cgi?id=471099
--- Comment #7 from tagwer...@innerjoin.org ---
> ... 'balooctl status' took quite a long time to return the result ...
Balooctl is looking through the index and counting the files that still need to
be indexed - at the same time as baloo is indexing and adding results to it.
The two do a little dance as to who gets access to the file....
One thing to double-check: Watch out whether you are using symlinks. Baloo
does not follow these when it discovers what needs to be indexed. If you've
created your text file in a folder "elsewhere" in your system and symlinked to
it, then it is not going to be indexed.
Second, there's a recent change (something that is being looked at again at the
moment) that caps the amount of memory that baloo can use. You might want to
check the:
/usr/lib/systemd/user/kde-baloo.service
file (if it exists...) If there's a memory limit is there as a:
MemoryHigh=512M
line, you can try changing it to:
MemoryHigh=50%
and see whether the indexing changes.
However the underlying problem is likely to be with BTRFS (and the fact that
when you reboot your disc might be mounted with a different device number - and
this makes baloo think that all your files are "new files"). It's worth looking
at Bug 470665.
--
You are receiving this mail because:
You are watching all bug changes.
