https://bugs.kde.org/show_bug.cgi?id=372650
--- Comment #5 from Philip Tuckey <philip.tuc...@free.fr> --- I gave the console error messages in the initial description, but I will upload a full console log asap. It seems to me that those error messages don't tell us whether the problem is a bug in Exiv2, or if digikam is providing bad data to Exiv2 (only occasionally of course). We would need digikam to print out the data each time it calls Exiv2. -- You are receiving this mail because: You are watching all bug changes.
