https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #9 from Gernot Hillier <ger...@hillier.de> --- Unfortunately, 5.8.0 pre-release as of today does NOT fix the issue for me. I still have photos which are not shown by digikam. Also, I don't think this is directly connected to bug 375483 any more. Even removing the uuid (exiftool -ImageUniqId= <file>) doesn't change anything. So far I found no rule when those files are visible in digikam and when not. With 5.7, I even had the same file (identical md5sum) twice under two different names in test directory "aa", one was visible, the other not. When moving them to another folder they both disappeared. So far, it seems this does only affect photos taken by my Samsung smartphone. So there's probably another weirdness in the way Samsung creates JPGs. When touching a visible and an invisible photo while digikam is running, stdout with 5.8 looks nearly identical: invisible file: digikam.general: Detected change, triggering rescan of "/home/gernot/sync/digibilder/to_sort/2017-08-xx Familie Landshut/" digikam.database: Starting scan! digikam.dimg: "/home/gernot/sync/digibilder/to_sort/2017-08-xx Familie Landshut/20170824_094516.jpg" : JPEG file identified digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2017-08-24 09:45:16.000 CEST Qt::TimeSpec(LocalTime)) digikam.metaengine: DateTime (Exif digitalized): Do. Aug. 24 09:45:16 2017 digikam.metaengine: Orientation => Exif.Image.Orientation => 6 digikam.metaengine: "/home/gernot/sync/digibilder/to_sort/2017-08-xx Familie Landshut/20170824_094516.jpg" ==> Read Iptc Keywords: () digikam.metaengine: Loading image history "" digikam.database: Scanning took 3 ms digikam.database: Finishing took 36 ms digikam.dimg: "/home/gernot/sync/digibilder/to_sort/2017-08-xx Familie Landshut/20170824_094516.jpg" : JPEG file identified digikam.metaengine: Orientation => Exif.Image.Orientation => 6 visible file: digikam.general: Detected change, triggering rescan of "/home/gernot/sync/digibilder/to_sort/2017-08-xx Familie Landshut/" digikam.database: Starting scan! digikam.dimg: "/home/gernot/sync/digibilder/to_sort/2017-08-xx Familie Landshut/20170824_091250.JPG" : JPEG file identified digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2017-08-24 09:12:50.000 CEST Qt::TimeSpec(LocalTime)) digikam.metaengine: DateTime (Exif digitalized): Do. Aug. 24 09:12:50 2017 digikam.metaengine: Orientation => Exif.Image.Orientation => 1 digikam.metaengine: "/home/gernot/sync/digibilder/to_sort/2017-08-xx Familie Landshut/20170824_091250.JPG" ==> Read Iptc Keywords: () digikam.metaengine: Loading image history "" digikam.database: Scanning took 6 ms digikam.database: Finishing took 38 ms digikam.dimg: "/home/gernot/sync/digibilder/to_sort/2017-08-xx Familie Landshut/20170824_091250.JPG" : JPEG file identified digikam.dimg: "/home/gernot/sync/digibilder/to_sort/2017-08-xx Familie Landshut/20170824_091250.JPG" : JPEG file identified digikam.metaengine: Orientation => Exif.Image.Orientation => 1 digikam.metaengine: Orientation => Exif.Image.Orientation => 1 The only difference is that "JEPG file identified" and the "Orientation" are printed *three* times for a working file while they are only printed *two* times for a file which is not shown in the UI. Does that somehow ring a bell for you? Any further idea how I could narrow down this issue? -- You are receiving this mail because: You are watching all bug changes.
