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 1295275 - Update comments in vncserver configuration file example
Summary: Update comments in vncserver configuration file example
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tigervnc
Version: 7.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1203710 1297830 1313485
TreeView+ depends on / blocked
 
Reported: 2016-01-04 04:47 UTC by amit yadav
Modified: 2019-12-16 05:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 01:29:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2237 0 normal SHIPPED_LIVE tigervnc bug fix and enhancement update 2016-11-03 13:28:30 UTC

Description amit yadav 2016-01-04 04:47:50 UTC 
Description of problem:

$ more /lib/systemd/system/vncserver@.service
  # The vncserver service unit file
  #
  # Quick HowTo:
  # 1. Copy this file to /etc/systemd/system/vncserver@.service
  # 2. Edit <USER> and vncserver parameters appropriately
  #   ("runuser -l <USER> -c /usr/bin/vncserver %i -arg1 -arg2")
  # 3. Run `systemctl daemon-reload`
  # 4. Run `systemctl enable vncserver@:<display>.service`


In step 2. of comment section, actually 2 lines need to be modified instead of just the first line

("runuser -l <USER> -c /usr/bin/vncserver %i -arg1 -arg2")

It should be 

ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024"
PIDFile=/home/USER/.vnc/%H%i.pid

Please update the Quick HowTo in comments to be consistent with RHEL documentation (https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-TigerVNC.html).

Version-Release number of selected component (if applicable):
tigervnc-server-1.3.1-3.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. N.A.

Actual results:
The vncserver configuration file suggest to modify <USER> in only one line. 
"runuser -l <USER> -c /usr/bin/vncserver %i -arg1 -arg2"

Expected results:
The vncserver configuration file should suggest to modify <USER> in following two lines:

ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024"
PIDFile=/home/USER/.vnc/%H%i.pid
Comment 2 Jan Grulich 2016-01-19 07:59:27 UTC 
Easy fix, can be fixed in RHEL 7.3.
Comment 3 Jan Grulich 2016-03-24 09:53:58 UTC 
Fixed in tigervnc-1.3.1-5.el7.
Comment 7 errata-xmlrpc 2016-11-04 01:29: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://rhn.redhat.com/errata/RHBA-2016-2237.html
Note You need to log in before you can comment on or make changes to this bug.