Bug 374012 - Binary "Exif.Photo.UserComment" converted to "METADATA-START" caption at import
Summary: Binary "Exif.Photo.UserComment" converted to "METADATA-START" caption at import
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Exif (show other bugs)
Version: 6.1.0
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-21 22:32 UTC by Blomi
Modified: 2020-08-23 07:04 UTC (History)
3 users (show)

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


Attachments
Image before and after the import (1.69 MB, application/zip)
2016-12-21 22:32 UTC, Blomi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Blomi 2016-12-21 22:32:30 UTC
Created attachment 102928 [details]
Image before and after the import

When importing images with binary UserComment the image caption is set to "METADATA-START".

I import an image via Import/Add Images which has a binary value in Exif.Photo.UserComment.
I select one image which hasn't a description yet and press "Download selected".
Afterwards in digikam this image has the caption "METADATA-START".
exiv2 output before:
Exif.Photo.UserComment                       Undefined 4104  (Binary value suppressed)

and afterwards:
Exif.Photo.UserComment                       Undefined  22  METADATA-START

I would expect digikam to either interpret the binary value or completely ignore it, but not to fill the captions with "METADATA-START".

exiv2 0.25 001900 (64 bit build)
Comment 1 caulier.gilles 2016-12-21 22:35:51 UTC
Please check if problem exists yet with 5.4.0 pre-release as Linux universal bundle. This one use Exiv2 0.26-svn which is not yet released but which introduce more than 200 bugfixes since Exiv2 0.25.

The bundle can be downloaded here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 2 Blomi 2016-12-24 13:03:38 UTC
The problems still exists in the 5.4.0 pre-release digikam-5.4.0-01-x86-64.
Comment 3 caulier.gilles 2019-03-20 15:16:12 UTC
After 3 weeks of work, i finally completed the compilation of AppImage using Qt
5.11.3 + QWebkit 5.212.

New 6.1.0 pre-release AppImage bundle can be found here (64 bits only for the
moment) :

https://files.kde.org/digikam/

Please check if this bugzilla entry still valid.

Thanks in advance

Gilles Caulier
Comment 4 Blomi 2019-03-30 20:20:22 UTC
Problem still exists in digikam-6.1.0-git-20190330T125338-x86-64.appimage
Comment 5 Maik Qualmann 2020-05-29 20:34:06 UTC
*** Bug 422240 has been marked as a duplicate of this bug. ***
Comment 6 caulier.gilles 2020-08-01 21:45:38 UTC
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best Regards

Gilles Caulier
Comment 7 Blomi 2020-08-03 19:15:59 UTC
Resolved with 7.0.0.
Now leaves the binary comment attribute untouched and shows "binary comment" in the GUI.

Thanks for this great software!
Comment 8 Maik Qualmann 2020-08-07 20:20:31 UTC
*** Bug 425125 has been marked as a duplicate of this bug. ***
Comment 9 Maik Qualmann 2020-08-23 07:04:21 UTC
Git commit 3b9b6615fd7b6a9711a5aa8986d143429bb31909 by Maik Qualmann.
Committed on 23/08/2020 at 07:02.
Pushed by mqualmann into branch 'master'.

filter "binary comment" from the comment fields
Since Exiv2-0.27.3 empty comment fields are
output as "binary comment".
Related: bug 425125, bug 422240

M  +11   -6    core/libs/metadataengine/engine/metaengine_exif.cpp

https://invent.kde.org/graphics/digikam/commit/3b9b6615fd7b6a9711a5aa8986d143429bb31909