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.
Description of problem: Bug 1259757 made a change to the default xstartup file generated when tigervnc is started for the first time that added the "-kill" option to the vncserver command. When using the default xstartup file with a minimal X server configured in .Xclients, the vncserver systemd service exits immediately.
Version-Release number of selected component (if applicable):
tigervnc-server-1.8.0-13.el7.x86_64
How reproducible: Consistently
Steps to Reproduce:
1. Set up VNC systemd service per https://access.redhat.com/solutions/966063 without setting up the xstartup file or starting the vncserver service.
2. Create an executable .Xclients file in the user's home directory containing the line '/bin/xterm &'.
3. Start the vncserver service.
Actual results:
VNC service is terminated immediately; 'systemctl status vncservice@:1' shows the service is stopped and no VNC process is running for the user.
Expected results:
VNC service runs and gives access to the GUI with the proper password.
Additional info:
This would seem to break VNC services for any minimal X server.
Comment 3Ray Strode [halfline]
2018-11-14 18:55:22 UTC
Does the ~/.Xclients file fail with startx as well ?
Does it start working with both startx and vnc if you drop the ampersand from the end?