Bug 492366 - Digikam does not write anymore xmp data to files from Pixel devices : debug shows an Exiv2 error.
Summary: Digikam does not write anymore xmp data to files from Pixel devices : debug s...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Xmp (show other bugs)
Version: 8.4.0
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-29 14:34 UTC by mahikeulbody
Modified: 2024-08-30 06:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 8.5.0
Sentry Crash Report:


Attachments
original file from Pixel 5 (2.35 MB, image/jpeg)
2024-08-29 14:34 UTC, mahikeulbody
Details
log file with the exiv2 error (34.63 KB, text/plain)
2024-08-29 14:35 UTC, mahikeulbody
Details
Pixel file after to the described process (2.35 MB, image/jpeg)
2024-08-29 14:37 UTC, mahikeulbody
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mahikeulbody 2024-08-29 14:34:58 UTC
Created attachment 173089 [details]
original file from Pixel 5

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY


STEPS TO REPRODUCE
1. Copy an original Pixel image (see attached) to a folder managed by Digikam
2. > digikam &> log.file
3. Check Exiftool to delegate metadata write setting
4. Check "Advanced" metadata mapping setting to default value
5. Type a title, for exemple <a text>
6. exiftool -xmp:title <file>   if "<a text>" retry step 5 with another text until exiftool does not find anymore an xmp-title
(that could take 3 or 4 times to retry)
7. exit digikam and check log.txt, seach for
digikam.metaengine: Exiv2 ( 3 ) :  Erreur XMP Toolkit 102: Unknown namespace prefix for qualified name
digikam.metaengine: Exiv2 ( 3 ) :  Failed to encode XMP metadata.

ADDITIONAL INFORMATION
Debug mode shows an error with Exiv2 (see attached log).
This problem happens also with a Pixel 5 and a Pixel 8.
It does not happen with my Ricoh GR II neither with photos taken with the same Pixel 5 last year ! (I presume the Pixel 5 has been updated to a new version of Android since last year).
Comment 1 mahikeulbody 2024-08-29 14:35:34 UTC
Created attachment 173090 [details]
log file with the exiv2 error
Comment 2 mahikeulbody 2024-08-29 14:37:01 UTC
Created attachment 173091 [details]
Pixel file after to the described process
Comment 3 mahikeulbody 2024-08-29 14:39:17 UTC
Same problem with the last Digikam 8.5 appimage.
Comment 4 Maik Qualmann 2024-08-29 16:39:34 UTC
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
Comment 5 Maik Qualmann 2024-08-29 16:43:09 UTC
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
Comment 6 mahikeulbody 2024-08-29 16:50:13 UTC
Thank you. I will check the fix when the related 8.5 appimage will be available and I will report the result here.
Comment 7 mahikeulbody 2024-08-30 06:20:37 UTC
Fixed. Thank you.