[digikam] [Bug 377418] Crash on saving metadata. Latest AppImage 5.5
https://bugs.kde.org/show_bug.cgi?id=377418 caulier.gil...@gmail.com changed: What|Removed |Added Platform|Other |Appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377418] Crash on saving metadata. Latest AppImage 5.5
https://bugs.kde.org/show_bug.cgi?id=377418 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|UPSTREAM|FIXED Version Fixed In||7.3.0 --- Comment #3 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377418] Crash on saving metadata. Latest AppImage 5.5
https://bugs.kde.org/show_bug.cgi?id=377418 caulier.gil...@gmail.com changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377418] Crash on saving metadata. Latest AppImage 5.5
https://bugs.kde.org/show_bug.cgi?id=377418 caulier.gil...@gmail.com changed: What|Removed |Added Component|Metadata|Metadata-Engine -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377418] Crash on saving metadata. Latest AppImage 5.5
https://bugs.kde.org/show_bug.cgi?id=377418 --- Comment #2 from wildcowboy --- (In reply to caulier.gilles from comment #1) > It's clear. It crash in Exiv2, XMP parser class, and finaly in Adobe XMP > SDK. Probably something from your image in XMP metadata is not well > interpreted by Exiv2. > > Reprot this problem as UPSTREAM to Exiv2 team with the image file for > investiguation (20161218_172327.jpg) > > Gilles Caulier Posted http://dev.exiv2.org/issues/1281 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377418] Crash on saving metadata. Latest AppImage 5.5
https://bugs.kde.org/show_bug.cgi?id=377418 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- It's clear. It crash in Exiv2, XMP parser class, and finaly in Adobe XMP SDK. Probably something from your image in XMP metadata is not well interpreted by Exiv2. Reprot this problem as UPSTREAM to Exiv2 team with the image file for investiguation (20161218_172327.jpg) Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
