Bug 433852 - digikam.metaengine: Cannot load metadata from file Error # 11: The file contains data of an unknown image type
Summary: digikam.metaengine: Cannot load metadata from file Error # 11: The file con...
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Engine (show other bugs)
Version: 7.2.0
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-02 11:27 UTC by benjcmin
Modified: 2021-05-22 07:18 UTC (History)
3 users (show)

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


Attachments
IMG_8386.HEIC (876.18 KB, image/heic)
2021-03-02 11:27 UTC, benjcmin
Details
GUI View (856.45 KB, image/png)
2021-03-02 11:27 UTC, benjcmin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description benjcmin 2021-03-02 11:27:09 UTC
Created attachment 136320 [details]
IMG_8386.HEIC

SUMMARY
digikam.metaengine: Cannot load metadata from file
Error # 11:  IMG_8386.HEIC: The file contains data of an unknown image type

STEPS TO REPRODUCE
1. Using picture attached 
2. generates the error # 11 in the logging
3. in GUI the Exif data is shown anyway


SOFTWARE/OS VERSIONS
macOS


ADDITIONAL INFORMATION
Comment 1 benjcmin 2021-03-02 11:27:53 UTC
Created attachment 136321 [details]
GUI View
Comment 2 Maik Qualmann 2021-03-02 11:30:21 UTC
This message is normal because Exiv2 does not support the HEIC file type (bug reports exist). We then read the metadata with libheif.

Maik
Comment 3 benjcmin 2021-03-02 11:40:15 UTC
Ok thx Maik, wasn't aware of this.
Comment 4 skeagy 2021-05-22 00:08:11 UTC
I would posit that this output is normal from the perspective of Exiv2, but a better behavior for digikam would be to suppress this logging output when libheif is detected. It might save other new users like me from some angst and wasted time trying to figure out what's wrong as I import thousands of pictures for the first time. Or at least add a note prominently in the top of the new user FAQ, as everyone who is new to digikam, running from an appImage via CLI, and using iPhones will experience this point of confusion. I can see how a regular GUI users might never see these logs if all is working well in a GUI, but I've got the standard error output from the CLI scrolling along at an alarming rate.

I am otherwise very hopeful for my future using this software and thank you for making it!
Comment 5 caulier.gilles 2021-05-22 07:18:02 UTC
Git commit 9a6eda6e22a967807a24937173a0fb0b8d03ca16 by Gilles Caulier.
Committed on 22/05/2021 at 06:12.
Pushed by cgilles into branch 'master'.

Be more explicit with exeption is generated from Exiv2 when file format is not supported. Polish error warnings

M  +1    -1    core/libs/metadataengine/engine/metaengine.cpp
M  +1    -1    core/libs/metadataengine/engine/metaengine_comments.cpp
M  +6    -3    core/libs/metadataengine/engine/metaengine_data_p.cpp
M  +27   -27   core/libs/metadataengine/engine/metaengine_exif.cpp
M  +3    -3    core/libs/metadataengine/engine/metaengine_fileio.cpp
M  +6    -6    core/libs/metadataengine/engine/metaengine_gps.cpp
M  +21   -21   core/libs/metadataengine/engine/metaengine_iptc.cpp
M  +11   -11   core/libs/metadataengine/engine/metaengine_item.cpp
M  +6    -6    core/libs/metadataengine/engine/metaengine_p.cpp
M  +4    -4    core/libs/metadataengine/engine/metaengine_previews.cpp
M  +22   -22   core/libs/metadataengine/engine/metaengine_xmp.cpp

https://invent.kde.org/graphics/digikam/commit/9a6eda6e22a967807a24937173a0fb0b8d03ca16