baloo_file don't follow the exclude filter from baloofilerc. Reproducible: Always Steps to Reproduce: 1. Add a new exclude filter at ~/.kde/share/config/baloofilerc (I add *.tre) Actual Results: baloo_file try to index files terminated with .tre: [code] ps aux | grep baloo_file_extractor joan 20719 77.8 7.1 642436 286416 pts/14 RN 18:00 0:14 /usr/bin/baloo_file_extractor 127316 127315 81447 81446 joan 20726 0.0 0.0 18400 916 pts/14 S+ 18:00 0:00 grep --color=auto baloo_file_extractor joan@jm-GNUlinux:~$ balooshow 127316 127315 81447 81446 Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) 127316 /home/joan/Documents/Dropbox/doctorat/Data/Phylogenies/Jetz et al 2012/AllBirdsEricson1.tre 127315 /home/joan/Documents/Dropbox/doctorat/Data/Phylogenies/Jetz et al 2012/AllBirdsHackett1.tre No index information found No index information found [/code] Expected Results: Baloo shouldn't try to index files terminated with .tre These files gives problems when indexed (see https://bugs.kde.org/show_bug.cgi?id=332421) and I have interrupted the indexing on these files some times. I'm running Kubuntu 14.04
Created attachment 86266 [details] baloofilerc with *.tre added as exclude filter
I'm having a similar issue but with entire excluded directories: - sudo killall -9 baloo_file baloo_file_extractor - less ~/.kde4/share/config/baloofilerc exclude folders[$e]=[...],$HOME/calibre/ (This wasn't added manually but via the kcm module - just in case there's some syntax error in there.) - [start] baloo_file - ps ax | grep [b]aloo_file_extractor 14475 pts/21 SN 0:01 /usr/bin/baloo_file_extractor 336359 [...] - balooshow 336359 336359 [$HOME]/calibre/ Conclusion: Exclusions are "challenged". ;-)
I also noticed that it seems that at least in the initial scan, exclusions are ignored (the cleaner, which I launched manually, does remove the excluded stuff, though). I know this is very vague and I can't seem to reproduce it either but I had baloo hog full io load for 30+ hours before I killed it, trying to index my storage drive containing an insane amount of small files, so I'm sure it happened :)
For me also baloo reproducible ignores an excluded folder (that means tries to index it). I had to exclude my entire home folder to stop this.
Baloo indexes stuff in 2 phases. Phase 1 - Index File url Phase 2 - Index content The checks if a file should be indexed were only done in Phase 1. So if you change the exclude filters manually, and do not run the cleaner, it is not removed from phase 1, and therefore is still passed to phase 2. With 4.13.1, phase 2 indexing also checks to see if the file should be indexed.
Baloo is happily indexing hundreds of thousands of files on my system that have explicit exclude rules. Neither the filters nor folders are being honored. This is with 5.104.0.
I missed the part about needing to call balooctl check. The help is very unclear about this.