Bug 453516

Summary: Crash on Inkscape svg file in Exiv2
Product: [Applications] digikam Reporter: Kaenguru <GenuesslichMysterioeserTapir>
Component: Metadata-EngineAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 7.6.0   
Target Milestone: ---   
Platform: Appimage   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 7.7.0
Sentry Crash Report:

Description Kaenguru 2022-05-07 18:46:08 UTC 
digikam constantly crashes on folders with certain svg files.
Tells me something about unknown filetype in .xerrors.log
This is very annoying, because those folders are not browsable.

[34mDigikam::MetaEngine::Private::printExiv2ExceptionError[0m: Cannot load metadata from file with Exiv2 backend: /home/xxxxxxxx/loorberkranz-02-haelften-blau.svg  (Error # 11 :  "/home/xxxxxxxx/loorberkranz-02-haelften-blau.svg: Die Datei enthält Daten eines unbekannten Bildtyps."


one of those files is here:
https://u.pcloud.link/publink/show?code=XZDYnpVZ1NLOKWcHvfumnJgj2F3smycVij97
It's just an ordinary Inkscape file


digikam 7.5 Appimage /digikam 7.6 Appimage
Linux (x86_64) release 5.4.0-109-generic

Doesn#t make a difference if I use digikam 7.5 or dk 7.6

System Info:
 OS: Linux Mint 20.1 x86_64 
 Kernel: 5.4.0-109-generic 
 Shell: bash 5.0.17 
 Resolution: 1920x1080 
 DE: MATE 
 WM: Metacity (Marco) 
 WM Theme: WinMe 
 Terminal: mate-terminal 
 CPU: Intel i5-4460 (4) @ 3.400GHz 
 GPU: NVIDIA GeForce GT 730 
 Memory: 32031MiB
Comment 1 caulier.gilles 2022-05-07 18:53:09 UTC 
Another entry where Exiv2 library crash again...

Please report this UPSTREAM problem on Exiv2 project from github. Don't forget to share a sample for the team.

https://github.com/Exiv2/exiv2/issues

Note : Exiv2 used on AppImage come from the 0.27-maintenance branch, not main branch.

Gilles Caulier
Comment 2 Maik Qualmann 2022-05-08 05:43:30 UTC 
Exiv2 can't read the file, but it doesn't crash. But the problem is the ImageMagick backend for metadata. Problem is already fixed for digiKam-7.7.0. See bug 451943

Maik