https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #48 from Tomas Trnka <tomastr...@gmx.com> --- Created attachment 159031 --> https://bugs.kde.org/attachment.cgi?id=159031&action=edit Patch making Baloo use the FSID as device ID Until somebody implements one of the fancy solutions proposed in the comments above, here is a fairly trivial stop-gap fix for the issue. With this patch, Baloo derives the device ID from the FSID instead of the device number. This fixes the issue completely for Btrfs and ext4 (where the FSID is derived from the UUID of the filesystem plus subvolume ID on Btrfs) while it does not hurt XFS and similar filesystems (where the FSID is just the device number, so nothing really changes). I'm going to submit a Gitlab merge request for this shortly, but here's the patch if anyone wants to try it out. For inspiration, here's a patched RPM built on Copr for Fedora: https://copr.fedorainfracloud.org/coprs/tootea/earlybird/build/5922301/ After installing a patched Baloo, things will be reindexed once (because all the device IDs will change) and then never again. It's best to run balooctl purge to first get rid of all the old duplicates with various device IDs (and logout to pick up the new libraries and make search work again). -- You are receiving this mail because: You are watching all bug changes.
