https://bugs.kde.org/show_bug.cgi?id=467550
Bug ID: 467550 Summary: baloo does not exclude folders under an excluded folder Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aar...@doofus.org Target Milestone: --- Created attachment 157406 --> https://bugs.kde.org/attachment.cgi?id=157406&action=edit File containing folders to be excluded SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install a large software package, i.e. Qt. 2. Start baloo 3. In a window run balooctl monitor 4. Run the command 'balooctl config add excludeFilters /home/[user]/Qt 5. Watch baloo continue to index in that folder OBSERVED RESULT Baloo will continue to index files in the excluded folder, even after restarting baloo. The folder is included in baloofilerc exclude folders[$e]=$HOME/Qt/ EXPECTED RESULT I expect Baloo to exclude any folders in the excluded folder list SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE 15.4/5.104.0 (available in About System) KDE Plasma Version: 21.8.29 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have some very large trees that should be excluded from Baloo indexing in part due to the sheer size, i.e. Qt source code, but this appears to be broken. For example, I want to exclude /home/username/Qt and all folders underneath it, however even though this folder is in the exclude list, Baloo happily continues to index this. I have well over 1,000,000 files in the excluded trees and this is consuming a significant amount of processing, memory, and disk space to index. Another bug claims that this is the expected behavior, which IMO is completely broken. There must be a way to be able to exclude large trees of files from Baloo!!! -- You are receiving this mail because: You are watching all bug changes.