Bug 16595

Summary:	identify command wrongly recognizes SVG/SVGZ format
Product:	Mageia	Reporter:	qu du <linnets>
Component:	RPM Packages	Assignee:	Shlomi Fish <shlomif>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, yann.cantin
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	imagemagick-6.8.9.9-4.mga5.x86_64	CVE:
Status comment:

Description qu du 2015-08-16 10:45:12 CEST

Description of problem:
'identify' command wrongly recognize SVG/SVGZ format as PNG

I installed the 'Cauldron' imagemagick-6.9.1.6-4.mga6.x86_64, doesn't has this problem.

Version-Release number of selected component (if applicable):
6.8.9.9

How reproducible:


Steps to Reproduce:
1. in konsole (any console application)
2. identify -format "%m" "FILE.SVG"
3.


Reproducible: 

Steps to Reproduce:

Comment 1 Yann Cantin 2015-08-20 01:49:18 CEST

Tested in mga5 x86_64 :

When Inkscape is installed :

identify -format "%m" SVG_logo.svg  -> PNG

Without Inkscape :

identify -format "%m" SVG_logo.svg  -> SVG

So, the bug is related to inkscape delegate.

As a workaround, you can 
- remove Inkscape from the system, 
or
- comment the relevant line in /etc/ImageMagick-6/delegates.xml (search for inkscape).

CC: (none) => yann.cantin

Comment 2 Samuel Verschelde 2015-09-09 09:12:50 CEST

Assigning to imagemagick and inkscape maintainer, Shlomi Fish.

Assignee: bugsquad => shlomif

Shlomi Fish 2015-09-09 12:06:57 CEST

Summary: identify command wrongly recognize SVG/SVGZ format => identify command wrongly recognizes SVG/SVGZ format

Comment 3 Shlomi Fish 2015-09-09 12:07:31 CEST

I can reproduce this on my MGA5-x86-64 VM, but I'm not sure how to fix it.

Shlomi Fish 2015-12-05 09:39:23 CET

Status: NEW => ASSIGNED

Comment 4 Marja Van Waes 2018-04-18 09:10:07 CEST

@ qu du,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 5 Marja Van Waes 2018-10-06 13:25:28 CEST

No reply, so closing as OLD.

@ qu du

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD