https://bugs.kde.org/show_bug.cgi?id=438382
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to skierpage from comment #0)
> Some baloo searches return the same file numerous times.
The filesystem you are using is critical here, have a look at:
https://bugs.kde.org/show_bug.cgi?id=402154#c12
Try checking the file with "stat" to see whether the device number / inode is
"stable" across reboots.
Baloo relies on the device number / inode internally, if a file appears with a
different ID, it's treated as a different file.
> ... make it appear N+1 times by deleting it on-disk and copying a backup
Maybe NTFS mounts don't have stable ID's. That would be an extra indication...
> 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.
> ... the behavior that deleting a file doesn't remove it from Baloo's index
> happens on an ext4 volume as well...
There are certainly times it doesn't, but I think mostly it does. It seems to
be an issue "referred to" under different bugs, might be something of interest
under Bug 353874, Bug 429006 and Bug 437754
--
You are receiving this mail because:
You are watching all bug changes.
