https://bugs.kde.org/show_bug.cgi?id=353874
--- Comment #18 from tagwer...@innerjoin.org ---
(In reply to trmdi from comment #17)
> When I download a file, baloosearch can't detect it until I manually index
> it with balooctl index. Is it a related bug, or does it need a delayed time
> before indexing new files ?
No, I don't think there's a delay.
Baloo should "pick up" a new or changed file immediately and put in the queue
for "full text" indexing. If you do a "balooctl index ..." you are telling
baloo to do it there and then.
If you are running on battery then I think baloo waits with the full text index
until the machine's plugged back in. I think that it also "backs off" on
indexing if it sees that the system is heavily used.
If baloo is not "immediately" noticing a new file then there's a bit of
troubleshooting to do. If it doesn't notice a change but it is found with a
"balooctl check", then it's worth looking at the inotify settings (particularly
if you are using Neon and have loads of folders). See what
sysctl fs.inotify.max_user_watches
says, if this is smaller than the number of folders you have then baloo won't
see changes as they happen.
Note that "balooctl index ..." does a one-off indexing of the file,
irrespective of whether it's in a folder you want indexed or not. External
discs are, for example, not automatically indexed but a "balooctl index ..."
would index a file on them.
There's a lot of bases to cover here, if the above doesn't help, maybe open a
new bug and include all the details.
--
You are receiving this mail because:
You are watching all bug changes.
