Red Hat Bugzilla – Bug 574362
xwdtopnm generates incorrect ppm output for xwd dump of an rdesktop screen
Last modified: 2018-10-27 09:58:18 EDT
Created attachment 400717 [details] patch based on upstream Description of problem: xwdtopnm produces incorrect ppm output for xwd dump of an rdesktop screen Version-Release number of selected component (if applicable): netpbm-10.35.58.x How reproducible: always Steps to Reproduce: 1. Connect to a Windows XP system using rdesktop: rdesktop 192.168.1.100 2.Get an xwd dump of the rdesktop screen by running the following command and selecting the rdesktop screen with the mouse: xwd -screen -frame > out.xwd 3. Convert the xwd dump to ppm format using xwdtopnm xwdtopnm out.xwd > out.ppm 4. View both images: display out.xwd display out.ppm Actual results: out.ppm has incorrect colors Expected results: out.ppm show show the correct image Additional info: * xwd, when run on the rdesktop window, generates a DirectColor image with 24bpp depth and BGR layout and MSB bit order. * The header on the xwd image however claims that the image has an RGB layout and LSB bit order., which leads the image colors to be read incorrectly by xwdtopnm * ImageMagick and Gimp read the image correctly, hence this is a bug in xwd which has been fixed upstream in netpbm 10.35.64 , thanks to Siddhesh for tracking this down, along with the patch
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0287.html