https://bugs.kde.org/show_bug.cgi?id=438382
--- Comment #2 from skierpage <skierp...@gmail.com> --- (In reply to tagwerk19 from comment #1) Thanks for responding 🤗. > (In reply to skierpage from comment #0) > > Some baloo searches return the same file numerous times. > ... > Baloo relies on the device number / inode internally, if a file appears with > a different ID, it's treated as a different file. Ding-ding, that's it. `baloosearch --id term` shows different IDs for the same path, e.g. % baloosearch --id FuelCellWorks 500d900000803 /media/Windows/Users/spage/Documents/ECO.txt 5be2000000803 /media/Windows/Users/spage/Documents/ECO.txt 8546e00000803 /media/Windows/Users/spage/Documents/ECO.txt ... > > Once this happens it seems impossible to clean up. > Yes, I have also noticed this. It seems that a file has to be "there" on > disc for "balooctl clear" to work and also (maybe?) the stored device number > / inode also has to match. It's worth following up. I filed bug 438527 , and may have spotted a logic error in `balooctl clear` 😻. I filed enhancement bug 438528 to add a `balooctl remove [ID...]` subcommand. -- You are receiving this mail because: You are watching all bug changes.
