https://bugs.kde.org/show_bug.cgi?id=515572
--- Comment #6 from [email protected] --- (In reply to Daniel from comment #0) > STEPS TO REPRODUCE > 1. Setup > exclude folders[$e]=$HOME/ > folders[$e]= > index contents=false but will be ignored. > only basic indexing=false > > 2. Add files like: > balooctl index "/home/sd/Media/Filme/_mkv/2067 Kampf um die Zukunft > (2020)/2067 Kampf um die Zukunft (2020).mkv" Apologies, I didn't read through your setup set by step, my original assumption was that there was something "deep" happening with .mkv files. First question - You are excluding your home drive and not adding any other folders for indexing? Then giving an "index contents=false" command, which I think doesn't exist but will be ignored together with am "only basic indexing=false", which switched from filename/metadata indexing to full text. I'm guessing you want to avoid automatic indexing (of anything, as you've not given any folders to index) and rely on manual commands to index files. That's an unusual setup. Second question - Is "/home/sd/" your home directory (not an SD disk or other external media?). If it is external media, can you say what filesystem - in fact it's probably a good idea to let us know what filesystems you are using anyway (ext4, btrfs, etc, etc) Third question - Does that happen just with .mkv files? or does the same happen if you copy and index, say, a .pdf? There are two "watch points": On some systems if you exclude $HOME without including any other folders, you get it included by default (so you see it both excluded and included). Second point is if you have not included a folder for indexing and then manually index one of the files in it. Baloo will "think" that the file no longer needs to be indexed and remove the entry. That alone *should* not leave you with a different set of results but maybe we've got more than one strange thing happening here... -- You are receiving this mail because: You are watching all bug changes.
