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.
(In reply to Jan Grulich from comment #1)
> I want to revert fix for 1259757 in RHEL 7.7 and RHEL 8.0, it causes more
> problems than it solves.
Jan we would need exception for this change, could you come up with some sort of justification? Thanks
-Tom
In RHEL 7.6, we fixed bug 1259757 by modifying xstartup script with adding "vncserver -kill $DISPLAY", which is supposed to automatically kill running session once previous process ends. This is working fine when using Gnome desktop, because it ends once user logs out. Problem is with minimal X server installations, where by default it runs /etc/X11/xinit/Xclients and based on what is installed, it runs for example "xterm &". With "&" appended at the end of the exec line it causes to automatically call "vncserver -kill $DISPLAY" which terminates tigervnc immediately. To solve the original issue (bug 1259757), users can simply add "-autokill" option to vncserver command.
Verified with with tigervnc-1.9.0-8.el8, defult xstartup generated like
#!/bin/sh
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
/etc/X11/xinit/xinitrc
# Assume either Gnome will be started by default when installed
# We want to kill the session automatically in this case when user logs out. In case you modify
# /etc/X11/xinit/Xclients or ~/.Xclients yourself to achieve a different result, then you should
# be responsible to modify below code to avoid that your session will be automatically killed
if [ -e /usr/bin/gnome-session ]; then
vncserver -kill $DISPLAY
fi