https://bugs.kde.org/show_bug.cgi?id=437019
--- Comment #1 from tagwer...@innerjoin.org ---
You are saying you see the count of "total files" in balooctl status go up?
Can you see the indexing happen if you run "balooctl monitor"?
You might have to disable baloo (balooctl disable) before you log
out, log back on, run "balooctl monitor" in a separate window and
then "balooctl enable" (and maybe a second time to get it going)
A possible thing to check is the number of "inotify" watches:
sysctl fs.inotify.max_user_watches
It can be that this is down as low as 8192. If you have a lot of
folders you might hit that limit and baloo will not see filesystem
changes. Should not be a problem with a recent kernel however you
can change this value as per
https://bugs.kde.org/show_bug.cgi?id=433204#c12
A further things to check (as baloo is somewhat dependent on the underlying
filesystem)
Run "stat oneofyourfiles" before moving the file and compare the
values to a "stat" after the file's been moved. If the device and
inode numbers are the same, then baloo ought to be able to match up
the file (even it it missed the inotify msg)
If you are running BTRFS (with subvolumes) you might find baloo
reindexing files after a reboot - not necessarily after a logon
Others may be able to give more definitive answers, these are just things I've
picked up as I've gone along...
--
You are receiving this mail because:
You are watching all bug changes.
