https://bugs.kde.org/show_bug.cgi?id=481101
--- Comment #2 from MarkW <instruf...@gmail.com> --- Thanks for your comprehensive reply. > There has to be something else messing with it, this is not the usual > behaviour... I'm stumped as to what is causing this TBH. > If it is disabled it generally stays disabled, and you can see the option in > the > .config/baloofilerc When I execute `balooctl disable`, `~/.config/baloofilerc` is updated by adding the following to the top of the file: > [Basic Settings] > Indexing-Enabled=false Once I reboot, the above is once again deleted from the file and baloo_file keeps running. > Keep an eye on this, see if it is being changed back. You could try setting > the config to "read only"... Making it read only once it is disabled works. Thanks! > * Do you see the snapshots "elsewhere" in the filesystem? Yes, these snapshots are elsewhere in the filesystem, but I specifically disabled `baloo` from indexing those locations a while back: ``` exclude folders[$e]=$HOME/.cache/,$HOME/.local/,/mnt/,/run/media/,/.snapshot/,/home/.snapshot;/config ``` > * If you do a "stat one-of-your-files.txt", do you see the device number > and inode of the file change (after the snapshot/reboot)? No, the device number and inode remain unchanged. > * If you do a "balooshow one-of-your-files.txt" do you see the DocID > change? (the Id is built from the device number and inode. The way this is > done has recently been changed to avoid reindexing, specifically in the BTRFS > case) No, the `DocID` stays the same. > * If you do a "baloosearch -i one-of-your-files.txt" do you get a single > result or many? I get a single result. -- You are receiving this mail because: You are watching all bug changes.
