Red Hat Bugzilla – Bug 431811
[RHEL5.2] X-server displays weird color
Last modified: 2010-10-22 18:18:50 EDT
Description of problem:
The X-server displays weird color when X-server is using big endian,
since the endian between VNC server and X-server is different.
I think the conversion of endian at gtk-vn is needed for this problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. use the X-server that is using big endian
The X-server displays weird color, see the attached file(with_bigendian.PNG).
The X-server displays normal color like native.
This is already fixed in Upstream of gtk-vnc.
Created attachment 294182 [details]
ScreenShot of Actual results
This is a regression wrt to RHEL-5.1 which displayed the colours normally.
This bugzilla has Keywords: Regression.
Since no regressions are allowed between releases,
it is also being proposed as a blocker for this release.
Please resolve ASAP.
NB, the patch quoted upstream solves one problem (big-endian vs little-endian
colours), but causes another problem (24 vs 16 bpp colour). We'll get a fully
operational patch for this from upstream soon...
This is actually a problem with the GTK-VNC widget.
Set dev ack for Dan.
Created attachment 298529 [details]
Fix endian conversions
Fix built into gtk-vnc-0.3.2-2.el5
What X server & OS platform is being used for the display ?
I have tested on a big-endian PPC display and it works correctly, so there must
be some further difference.
Please provide output of 'xdpyinfo' on the display being used for testing.
I have now reproduced the problem.
My previous fix addressed the case where GTK-VNC was running ona big-endian
machine, and the X display was on a big-endian machine, with the VNC server on
The scenario reported here is slightly different - GTK-VNC is running on a
little-endian machine, but displayed on an X server on big-endian, and using VNC
server on little-endian. This combination is not operating correctly.
I am working on a fix for this problem
Fixed in gtk-vnc-0.3.2-3.el5
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.