Most of my folders and sub-folders are OK, but one in particular (named "27" according to the 27th days of March) shows a count of 2 photos ("27 (2)") but actually doesn't display them when I click on it. Neighbor sub-folders are actually showing the count and display them when clicked without problem. It seems to be related to the JPEG files themselves, because when I put inside another JPEG file, this one get displayed (and the count is well increased by 1). Therefore, I attached one of these files, "IMG_20160327_112818.jpg". I didn't have this problem with previous Dikigam 4.x! Reproducible: Always Steps to Reproduce: 1. Copy the file "IMG_20160327_112818.jpg" in a folder ; 2. Ensure that folder's count is increased ; 3. Enter the folder. Actual Results: The copied file is not displayed at all, while other are. Expected Results: It must be displayed, just like others. The JPEG has been taken with a smartphone Samsung Galaxy.
Created attachment 100692 [details] This JPEG file cannot be displayed by Digikam 5.1.0 Forgot to state it, but this JPEG is displayed by Gwenview without any problem. I initially tagged it with Digikam 4.14.0 (see it's metadata).
Still exists with 5.2.0.
Can you reproduce the problem using digiKam Linux AppImage bundle ? The last bundle is available at this url: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier
Yes, with the AppImage of DK 5.4.0 I can reproduce this bug.
Please enable this option for testing: Settings->Image Editor->Versioning->Always show original images Maik
Thanks Maik! "Always show original images" did not help, but "Always show intermediate snapshots" (tentative translation from French) actually solved the problem, and these photos get displayed. It's weird, though, because I don't remember having edited these photos. Actually, if I display the "Versions" tab (from the right panel), it displays about 250 "identical images" which are absolutely not identical! Filenames and actual images are completely differents. What's going on?!
Probably the data in database about versioning are corrupted. Gilles Caulier
How could I fix it?
Write database contents to image metadata. Remove database and re-scan whole collection. Database will be restored from image metadata. Of course make a backup before. Gilles Caulier
The cause of this bug is now known and the bug with the Samsung UniqueID is fixed (Bug 375483). I close this bug now. Maik