https://bugs.kde.org/show_bug.cgi?id=267131
--- Comment #30 from Maik Qualmann <metzping...@gmail.com> --- When I read SQLiteBrowser in this context, I feel dizzy. The update function in the collection settings does exactly what it's supposed to do. I often use it to test different scenarios or reproduce bugs. We've already fully enabled the new file UUID for network drives. Not yet for local hard drives and removable media; there's still a fallback to the partition UUID. There are various reasons for this, e.g., support for read-only media/partitions. A collection that isn't recognized won't be scanned. New hard drives that haven't been formatted are problematic, as they can contain the same partition UUID. Image tags can also be lost with a new setup, e.g., if sidecars are used but reading from sidecars was forgotten. Maik -- You are receiving this mail because: You are watching all bug changes.
