Summary: | imagemagickLoader and wmf files | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Kaenguru <GenuesslichMysterioeserTapir> |
Component: | Plugin-DImg-Magick | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, metzpinguin |
Priority: | NOR | ||
Version First Reported In: | 7.2.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.5.0 | |
Sentry Crash Report: | |||
Attachments: |
sample wmf file
Components used screenshot Version Info |
Description
Kaenguru
2021-03-31 18:17:44 UTC
The WMF file generates this exception in the AppImage: 3139.wmf" ] digikam: NonconformingDrawingPrimitiveDefinition `0' @ error/draw.c/RenderMVGContent/4348 Maik Kaenguru : https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_imagemagick/CMakeLists.txt ... is for the AppImage bundle build and... it's have no relation with your Ubuntu package Also as Maik said, the AppImage that we provide is compiled with WMF support. if no explicit option is passed to configure IM, the option is turned on by default. So, it's not a DK problem do far for me... Gilles Caulier The IM version used by digiKam can be found in Help/Components Info dialog. Please check if your IM CLI tool as identify, your WMF file can be open without error. Gilles Caulier Created attachment 139601 [details]
Components used screenshot
Created attachment 139602 [details]
Version Info
My locally installed imagemagick identifies as: identify Version: ImageMagick 7.0.9-1 Q16 x86_64 2019-10-30 https://imagemagick.org But this is not what the appimage uses, as you can see from the attached screenahot. https://bugs.kde.org/attachment.cgi?id=139601 (Sorry if I can't handle attachments here properly, feel free to correct. I'm not used to this system) Imagemagick 7.x can handle my wmf files (for example using display filename.wmf) , IM 6.x can't. This problem will be fixed when AppImage will be ported from Mageia6 to Mageia7 after 7.3.0 release. Gilles Caulier Problem fixed with AppImage 7.5.0 build under Mageia7 |