Bug 499466

Summary:	Using Exiftool to write tags corrupts the ICC Profile of the image.
Product:	[Applications] digikam	Reporter:	moritz.haseloff
Component:	Metadata-ExifTool	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version First Reported In:	8.5.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:	8.6.0
Sentry Crash Report:
Attachments:	uncorrupted file corrupted file screenshot with corrupted image

Description moritz.haseloff 2025-02-03 15:33:52 UTC

Created attachment 177926 [details]
uncorrupted file

SUMMARY
I am delegating tag writing to exiftool because I want to write tags to HEIC images. Writing tags corrupts the ICC Profile of the image (it deletes it), rendering the image in overbright/high contrast colors. See the bugreport for exiftool here: https://github.com/exiftool/exiftool/issues/313

STEPS TO REPRODUCE
1. set digikam to delegate tag writing to exiftool
2. load uncorrupted file
3. write a face tag to the image

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 moritz.haseloff 2025-02-03 15:34:29 UTC

Created attachment 177927 [details]
corrupted file

Comment 2 moritz.haseloff 2025-02-03 15:35:10 UTC

Created attachment 177928 [details]
screenshot with corrupted image

Comment 3 moritz.haseloff 2025-02-03 15:35:46 UTC

Phil, the developer of exiftool released a new version with a partial fix, it might be worth adding it to digikam 8.6.0. 
Thank you!

Comment 4 caulier.gilles 2025-02-03 15:42:08 UTC

Which ExifTool version exactly. In next 8.6.0, We integrate Exiftool 13.12...

Gilles Caulier

Comment 5 Maik Qualmann 2025-02-03 16:59:09 UTC

The cause is not ExifTool. Therefore, nothing should be changed in ExifTool. The cause was Bug 498076.

Maik

Comment 6 moritz.haseloff 2025-02-03 17:02:47 UTC

Wow, thanks I was not able to find this issue.