RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

VNC Extersion is missed upon Xorg server re-generation i.e. when all the clients running on X server exits. 

Version-Release number of selected component (if applicable):
tigervnc-server-module-1.1.0-14.el6.i686
xorg-x11-server-Xorg-1.15.0-15.el6.i686

How reproducible:
Always

Steps to Reproduce:
1. Boot system in runlevel 3
2. Configure xorg.conf to load vnc module
3. Start Xorg and run xterm on it
 Xorg & DISPLAY=:0 xterm
4. In xtern window make sure VNC-EXTENSION is loaded.
 xdpyinfo | grep VNC
5. Try connecting from other system using vncviewer and make sure it works.
6. Exit from xterm and observe server regeneration happeing there. Slight flicker of Xorg due to re-load.
7. Send xterm to this Xorg from ssh session
 DISPLAY=:0 xterm
8. Check if VNC-EXTENSION is displayed on the server.
 xdpyinfo | grep VNC
9. Try connecting again from other system using vncviewer

Actual results:
No VNC-EXTENSION after server regeneration and remote system can not connect to X server over vnc.

Expected results:
VNC-EXTENSION should be retained/re-loaded after server regeneration and remote system should be able to connect to X server over vnc.


Additional info:

I see the same thing. I think it's caused by the fix for bug #1004093.

With the RHEL-6.6 tigervnc package I can't connect xterm a second time.

Investigating.

Also happens with Red Hat Enterprise Linux 7.0.

Reported upstream.

This is now fixed upstream.

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-2014-1412.html