Red Hat Bugzilla – Bug 213281
vnc vncconnect / vncconfig -connect doesn't work
Last modified: 2013-04-30 19:34:40 EDT
Description of problem:
I encountered this issue when performing a vnc install using vncconnect, it
reports 'Connected!' - but it's not. netstat -t shows no connection, the
workstation sees no connection. At the shell on the box being installed, if I
manually run 'vncconfig -display :1 -connect (workstation ip)' I get a protocol
error. NOTE: this is on x86_64; it's not an issue w/ normal x86.
Here's the error:
X Error of failed request: BadLength (poly request too large or internal Xlib
Major opcode of failed request: 134 (VNC-EXTENSION)
Minor opcode of failed request: 7 ()
Serial number of failed request: 7
Current serial number in output stream: 7
Also note this issue is actually likely with 'vnc-server'
Steps to Reproduce:
1. Run 'vncserver'
2. Run 'vncconfig -display :1 -connect (some host addr)'
Error message, no connect
please, could you specify which version of vnc are you using?? I've fixed
vncconfig crash problem in vnc-4.1.2-4.el5 or vnc-4.1.2-5.fc6. Can you please
try to reproduce this bug with one of these packages??
These are version 4.1.2-3. I'll try this out on the newer versions later today.
Will the next RHEL5 beta/release automatically get the newer version?
patch will be avaliable very soon. Could you please test this package?? I think,
this problem is fixed here. Thank you
you can update to vnc-4.1.2-4.el5 in rhel5-beta2 now. I think this bug is fixed
here. Could you try to reproduce it??
ok, I was finally actually able to get hold of beta 2 today, and can verify that
it's fixed for 64bit now. The fixed version is 4.1.2-4.el5, as shown above.