Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
When using TigerVNC as a loadable X module, initialisation of the GLX extension was not performed correctly. This could lead to the X server crashing. A fix from a later version of tigervnc has been backported, and the GLX extension is now initialised correctly.
Description of problem:
Xorg crashes upon vnc access after upgrade of tigervnc-server-module package
The session works well when xorg.conf is configured not to use VncAuth
Option "SecurityTypes" "None"
but Xorg crashes immediately upon closure of vnc client window when VncAuth is not used
Version-Release number of selected component (if applicable):
tigervnc-server-module-1.1.0-5.el6_4.1
How reproducible:
Always
Steps to Reproduce:
1. Configure xorg based vnc access with current tigervnc-server-module
2. connect from remote system using vncviewer
3. observe Xorg crash on system console
Actual results:
Xorg crashes upon vnc access
Expected results:
Xorg should not crash
Additional info:
Reverting to earlier version helps to workaround issue.
Seems to be regression caused by Bug #950708https://bugzilla.redhat.com/show_bug.cgi?id=950708#c16
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
Description of problem: Xorg crashes upon vnc access after upgrade of tigervnc-server-module package The session works well when xorg.conf is configured not to use VncAuth Option "SecurityTypes" "None" but Xorg crashes immediately upon closure of vnc client window when VncAuth is not used Version-Release number of selected component (if applicable): tigervnc-server-module-1.1.0-5.el6_4.1 How reproducible: Always Steps to Reproduce: 1. Configure xorg based vnc access with current tigervnc-server-module 2. connect from remote system using vncviewer 3. observe Xorg crash on system console Actual results: Xorg crashes upon vnc access Expected results: Xorg should not crash Additional info: Reverting to earlier version helps to workaround issue. Seems to be regression caused by Bug #950708 https://bugzilla.redhat.com/show_bug.cgi?id=950708#c16