Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 736840 - ImageMagick transparency handling broken
Summary: ImageMagick transparency handling broken
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ImageMagick
Version: 15
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Pavel Alexeev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-08 20:13 UTC by Jos Vos
Modified: 2011-09-09 08:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-09 07:15:35 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jos Vos 2011-09-08 20:13:58 UTC 
Description of problem:

The F15 ImageMagick has a broken transparency handling in some cases.  For example the simple command "convert -size 100x100 xc:transparent out.png" does not generate a transparent image anymore.  This worked fine in F14.

AFAICS the changelog for a 6.6.6.x release of ImageMagick mentions this problem, so a newer version might solve the problem.

Version-Release number of selected component (if applicable):
6.6.5.10-19.fc15

Please release an update of ImageMagick for F15.
Comment 1 Pavel Alexeev 2011-09-09 07:15:35 UTC 
Thanks for the bugreport, meantime in rawhide already new version - http://koji.fedoraproject.org/koji/buildinfo?buildID=259788
Comment 2 Jos Vos 2011-09-09 08:13:55 UTC 
I already saw that rawhide had a new version, but as this bug is pretty serious (it seems to occur in many cases when PNG transparency is involved), I hoped to trigger an official F15 update.
Comment 3 Pavel Alexeev 2011-09-09 08:30:16 UTC 
I'm doupt it is so seriouce bug to initiate all dependency rebuild for that. If you insist, you may wich create ticket on FESCO for that. Or initially discuss about it in ML.
Note You need to log in before you can comment on or make changes to this bug.