Legacy ImageMagick Discussions Archive

Awesome!

The bug still occurs on "ImageMagick 6.8.6-3 2013-08-02 Q16" - behavior appears identical.

I did run the original command. The whole point of the base64 thing was just to workaround the fact that this bug-hosting bulletin board website doesn't allow for file uploads. I have no convenient place to freely host it, so I just attached it as a base64 file. Any platform that can run ImageMagick ...

Sorry, I accidentally assumed a certain type of unix command knowledge there. To recreate the original pcx file on disk, run the following command `base64 -d | bzip2 -d > in.pcx` then paste the base64 text blob, then hit CTRL-D twice. (By the way, don't use the "Select all" link that this bulletin ...

That version is the latest available on the OS. I didn't try compiling a custom one. See the original post for a PCX file that reproduces the problem.

(I haven't tried every other conversion, but just now for that same file I tried converting to png and that appears to be accurate.) Also, this was using the yum binaries on "Fedora release 17 (Beefy Miracle)".

Note that this can be verified merely be running `identify -verbose in.pcx out.pcx` and looking at the "Histogram:" lines. The latter one will have only black. It can also be seen in an image viewer, which will show an all black image as well.

Running `convert in.pcx out.pcx` causes a valid out.pcx file with the same dimensions to be generated, but every pixel has been changed to black. This only happens on certain pcx files, though I'm not certain what might be unique about them. Version: ImageMagick 6.7.5-6 2012-08-11 Q16 Here's a ...