Summary: | Sub-folder count images but don't show them (unsupported JPEG file?) | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Mathieu MD <mathieu> |
Component: | Albums-MainView | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, mathieu, metzpinguin |
Priority: | NOR | ||
Version: | 5.2.0 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 6.0.0 | |
Sentry Crash Report: | |||
Attachments: | This JPEG file cannot be displayed by Digikam 5.1.0 |
Description
Mathieu MD
2016-08-20 06:23:55 UTC
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 |