https://bugs.kde.org/show_bug.cgi?id=375483
Gernot Hillier <ger...@hillier.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ger...@hillier.de
--- Comment #14 from Gernot Hillier <ger...@hillier.de> ---
I was also hit by this nice interpretation of a "unique id" by Samsung.
But for me, re-scanning metadata for old samsung photos already known to
Digikam does NOT heal all internal database inconsistencies with Digikam 5.8.
I found that such images were falsely internally tagged as "originalVersion" by
Digikam which hides them from the album preview (unless you enable "always show
original images" in Settings > Image Editor > Versioning).
See bug 354819 for further details of my journey.
By the way, during my travel inside digikam4.db, I also noticed that the
ImageHistory table also still knows the old, problematic uniqueId for my
Samsung photos. Not sure if this could also harm someday.
--
You are receiving this mail because:
You are watching all bug changes.
