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:
- In XDMCP over VNC sessions, Gnome exits and returns to GDM login screen arbitrarily with no errors reported.

Version-Release number of selected component (if applicable):
- tigervnc-server-1.1.0.18

How reproducible:
- I have not been able to reproduce this in house, however I have personally observed this behavior on the affected system via remote session. This issue does not occur after downgrading to tigervnc-server-1.1.0.16, and leaving everything else alone. This has been reproduced using multiple VNC clients, windows/linux. The primary use case is VNC port forwarded through a SSH session. This does not seem to be relevant as I have not been able to make the sesion fail using this type of connection, however I have not been able to make it fail on a direct connection either. One of our SMEs has not been able to reproduce the issue either.

Target machine is a VMWare guest, however it is reproducable on both ESX 5.5 and 6 in the customer's environment, so this does not seem to make a difference

Steps to Reproduce:
1. Connect to system via VNC viewer
2. After a few minutes (3 to 5) Gnome will die
3.

Actual results:
- Gnome session fails

Expected results:


Additional info:

Possible duplicate of bug 1344137?

Could someone please test this scratch build:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11739991

Also update to latest xorg-x11-server which is xorg-x11-server-1.17.4-12.el6 and latest mesa-libGL which is I guess mesa-libGL-11.0.7-4.el6.

Try it please ASAP, the build will be removed soon.

*** This bug has been marked as a duplicate of bug 1344137 ***