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.
Bug 1506273 - regression: unit file shipped with tigervnc-server-1.8.0-1 unusable
Summary: regression: unit file shipped with tigervnc-server-1.8.0-1 unusable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tigervnc
Version: 7.4
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
: 1481428 1521186 1534270 (view as bug list)
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2017-10-25 14:33 UTC by Joe Wright
Modified: 2022-03-13 14:30 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 11:37:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3167971 0 None None None 2017-10-30 09:02:32 UTC
Red Hat Knowledge Base (Solution) 3224641 0 None None None 2017-10-25 14:50:52 UTC
Red Hat Product Errata RHBA-2018:0722 0 None None None 2018-04-10 11:38:15 UTC

Description Joe Wright 2017-10-25 14:33:36 UTC 
Description of problem:
- the unit file shipped with tigervnc-server-1.8.0-1 does not work. 

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

How reproducible:
- 100%

Steps to Reproduce:
1. Install tigervnc-server-1.8.0-1
2. configure unit file with desired user name and port
3. complete additional vnc configuration (vncpasswd, firewall and whatnot)
4: enable the daemon
5: start the daemon
6: connect to the configured daemon

Actual results:
- Black screen with icons if you use the default ~/.vnc/xstartup file
- totally black screen if you configure the xstartup file to call gnome via dbus-launch

Expected results:
- VNC works normally

Additional info:
- Clobbering the new unit file with a prior version of the unit file fixes the problem. The issue appears to lie with the [Service] section of the file, which is currently:

------------------------------------------------------
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target

[Service]
Type=forking
User=<USER>

# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=-/usr/bin/vncserver -kill %i
ExecStart=/usr/bin/vncserver %i
PIDFile=/home/<USER>/.vnc/%H%i.pid
ExecStop=-/usr/bin/vncserver -kill %i

[Install]
WantedBy=multi-user.target
-------------------------------------------------------

It should be:
-------------------------------------------------------
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target

[Service]
Type=forking
# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
ExecStart=/sbin/runuser -l <USER> -c "/usr/bin/vncserver %i"
PIDFile=/home/<USER>/.vnc/%H%i.pid
ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'

[Install]
WantedBy=multi-user.target
--------------------------------------------------------

Replacing the unit file resolves the problem in my testing (with obvious replacement of <USER> with my local user on my test system)

The main issue seems to be the changes to the [Service] section in the latest version.
Comment 6 Jan Grulich 2017-10-27 09:23:36 UTC 
Fixed in tigervnc-1.8.0-4.el7.
Comment 8 Jan Grulich 2017-10-30 09:02:33 UTC 
*** Bug 1481428 has been marked as a duplicate of this bug. ***
Comment 9 Jan Grulich 2017-12-06 07:35:14 UTC 
*** Bug 1521186 has been marked as a duplicate of this bug. ***
Comment 10 Trevor Hemsley 2018-01-14 16:40:34 UTC 
Issue as described with the new unit file is solved by adding 

PAMName=login

in the [Service] section. As shipped, the file lacks this and journalctl shows an error being issued by the startup

Jan 13 15:09:48 centos7.trevor.local gnome-session[26311]: gnome-session-binary[26311]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.

This is because it's defaulting to using a PAM session that doesn't include the pam_systemd.so line.
Comment 11 Jan Grulich 2018-01-15 06:01:53 UTC 
*** Bug 1534270 has been marked as a duplicate of this bug. ***
Comment 13 Tomas Hudziec 2018-02-08 14:48:38 UTC 
With tigervnc-server-1.8.0-4.el7.x86_64 in RHEL7.5 Beta I can see screen correctly, except that gnome-shell does not start. The bug 1543073 may be related to it.
Comment 17 errata-xmlrpc 2018-04-10 11:37:45 UTC 
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.

https://access.redhat.com/errata/RHBA-2018:0722
Note You need to log in before you can comment on or make changes to this bug.