| Summary: | Digikam does not write anymore xmp data to files from Pixel devices : debug shows an Exiv2 error. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | mahikeulbody <51mfxqck> |
| Component: | Metadata-Xmp | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/-/commit/d4187537cdb81608d88a0348c186b25de7281d6f | Version Fixed/Implemented In: | 8.5.0 |
| Sentry Crash Report: | |||
| Attachments: |
original file from Pixel 5
log file with the exiv2 error Pixel file after to the described process |
||
|
Description
mahikeulbody
2024-08-29 14:34:58 UTC
Created attachment 173090 [details]
log file with the exiv2 error
Created attachment 173091 [details]
Pixel file after to the described process
Same problem with the last Digikam 8.5 appimage. Git commit d4187537cdb81608d88a0348c186b25de7281d6f by Maik Qualmann. Committed on 29/08/2024 at 16:38. Pushed by mqualmann into branch 'master'. register more Google container/item namespaces created by ExifTool FIXED-IN: 8.5.0 M +1 -1 NEWS M +18 -9 core/libs/metadataengine/engine/metaengine.cpp https://invent.kde.org/graphics/digikam/-/commit/d4187537cdb81608d88a0348c186b25de7281d6f You also see this Exiv2 bug as the cause: https://github.com/Exiv2/exiv2/issues/2932 We can register the namespaces, but programs from Adobe or ExifTool create their own Google container names. Maik Thank you. I will check the fix when the related 8.5 appimage will be available and I will report the result here. Fixed. Thank you. |