The GraphicsMagick 1.3.13-3 F-16 update breaks some, but not all PNGs. The broken ones appear as if some vertical empty space/interlacing was added to them. No such problems with earlier GraphicsMagick versions.
Some reproducer files attached.
Created attachment 560057 [details]
Reproducer PNG broken by 1.3.13 update
Created attachment 560058 [details]
Reproducer PNG as shown by "gm display" from 1.3.13
So, the png in comment #1 was created by gm or is the source used in comment #2?
The PNG in comment 1 is just a random PNG that GM 1.3.13 has problems with, no idea what it was created with.
The PNG in comment 2 is a screenshot of how the PNG from comment 1 looks with GM 1.3.13's "gm display" (I should probably have attached this one as a BMP or something else than PNG to reduce confusion).
I'll see if the impact is limited to or goes beyond the use of 'gm display'
OK, GM-1.1.13 does not like this image alright, pretty much any operation botches it.
Bug opened upstream,
I'll see about diff'ing gm-1.1.12 -> 1.1.13 coders/png.c for anything obviously wrong. it was updated to support libpng-1.5 (as in rawhide, but apparently there's some regression going on here with f16/libpng-1.2.x)
I am able to reproduce the problem here as well. I see the same problem with libpng 1.5.6 and libpng 1.2.46. While there were a number of known problems with the PNG writer, this is the first issue I am aware of with the reader.
confirmed still an issue with 1.3.14
*** Bug 803578 has been marked as a duplicate of this bug. ***
Any progress on this or thoughts when it might be fixed?
this has been reported upstream,
and it's been acknowledged/confirmed (see Bob's comment #8 as well as that referenced in the upstream report).
I am hoping that Glenn Randers-Pehrson will be able to complete the fixes to (or rewrite of) GM's png.c. Progress has been slow since he would like to do the job correctly and has other responsibilities. It seems likely that the issues were introduced due to the port to libpng 1.4.X and then libpng 1.5.X.
*** Bug 812645 has been marked as a duplicate of this bug. ***
Confirmed still an issue with 1.3.16.
GraphicsMagick-1.3.17-1.fc17 has been submitted as an update for Fedora 17.
GraphicsMagick-1.3.17-1.fc16 has been submitted as an update for Fedora 16.
GraphicsMagick-1.3.17-1.el6 has been submitted as an update for Fedora EPEL 6.
GraphicsMagick-1.3.17-1.el5 has been submitted as an update for Fedora EPEL 5.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing GraphicsMagick-1.3.17-1.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Quick testing seems to indicate this new testing version 1.3.17-1 does not cause the problems that were associated with 1.3.13-3, will leave feedback.
GraphicsMagick-1.3.17-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.