https://bugs.kde.org/show_bug.cgi?id=477154
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to Lucy June Schonder from comment #3)
> I use the XFS for Root and BtrFS for Home ;-)
My guess in that case is that you have the BTRFS partition mounted with a
different device number. It can (easily) be that, if you are using BTRFS and
have multiple subvolumes, the partition "appears" with a different minor device
number on a reboot as the of a race during the initial (parallel) mount.
Baloo uses a combination of the device number and inode as its internal
Document ID. If it sees a file, even one it has seen before, appearing with a
different device number it thinks it is a new file and indexes it again. It has
been OpenSUSE users who have suffered most from this but recently also Fedora.
A fix for this has landed with Frameworks 5.111. Not a perfect fix but I think
reasonable enough...
--
You are receiving this mail because:
You are watching all bug changes.
