https://bugs.kde.org/show_bug.cgi?id=526391
--- Comment #2 from [email protected] --- (In reply to tagwerk19 from comment #1) > (In reply to kde from comment #0) > > ... Except the "Not running, 0% complete" message in System Settings... > That sounds as if Baloo hasn't started (at all).. > > Can you see if there's a process running and/or what "$ systemctl --user > status kde-baloo" says? baloo is running, that error seemed to be transient as I was messing with things. I believe the larger issue is that it hard-stops at FUSE mounts regardless of explicit inclusion. I understand why this change was made but I would be interested in it being optional, and in having a setting per-directory to either allow or disallow content indexing. (For my use case, only filename retrieval is desired, but others may have small network shares that they would like content indexing on.) -- You are receiving this mail because: You are watching all bug changes.
