https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #14 from Gernot Hillier <ger...@hillier.de> --- Ok, I'm one large step ahead: all problematic images are internally tagged as "Original Version" despite I surely never edited those files: sqlite> select * from ImageTags where imageid in (93042); 93042|112 sqlite> select * from Tags where id=112; 112|110|Original Version|0| I can either delete the wrong internal tag: delete from ImageTags where imageid in (select id from Images where name="20170907_102007.jpg"); or enable the "always show original version" setting in digikam. My theory: During initial import from the Samsung smartphone, the files had the non-unique ImageUniqueID in EXIF data which Samsung deliberately uses to confuse people. Due to importing several files with the same unique ID, digikam somehow internally thought they are related and tagged some of them internally as "original version". Now, we could do what we want: manually change/remove EXIF ImageUniqueID field, internally create own uniqueIDs for it, moving the file away and back to digikam folders - this would never remove the internal originalVersion tag again. Is it possible that those pictures received this flag because they -- You are receiving this mail because: You are watching all bug changes.
