Red Hat Bugzilla – Bug 203673
Xvnc: SProcShmCreatePixmap() fails to byte-swap 'pid'
Last modified: 2013-04-30 19:34:01 EDT
Description of problem:
A bug in the main Xorg source prevents clients properly working with the server
in some cases when shm is used, if the client and server are running in
different endianness. The bug is fixed in the latest Xorg source, but the
vnc-server also needs to be updated.
Version-Release number of selected component (if applicable):
Always, when using a suitable client on a server with the vncserver running in a
A complaint from X that the id is incorrect, something like this:
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this
(Details: serial 137 error_code 14 request_code 129 minor_code 5)
Should work as normal, as the rest of the code supports clients whose endianness
doesn't match the server.
The patch has already been accepted into the main X server tree. I can't find a
source package for the vnc server so I couldn't create a new patch against that.
could you try to reproduce this bug with latest version of vnc, please??
I was using vnc-126.96.36.199, is there a later version I can try? I had looked
briefly at RealVNC, which I think is what you use, but it looked as though this
doesn't include the X server itself, and the bug exists in the X server code
that vnc is built against. I do know that the patch has been included in the
cvs for tight-vnc.
I've checked + imported your patch
Fix can be avaliable in next release of vnc (4.0.9)
Did this make it into RHEL4.5 beta? This seems to include 4.0.11, but I can't
see the fix in there.
(In reply to comment #5)
Patch will be in 4.6 . It was too late to include it in 4.5
Created attachment 158510 [details]
The attached patch (158510) doesn't appear to relate to this bug...
Created attachment 158512 [details]
I've attached wrong file, correct patch
(In reply to comment #10)
> The attached patch (158510) doesn't appear to relate to this bug...
Yeah, my mistake.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
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 therefore 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.