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:
Undocumented change in behaviour between vncserver command shipped in RHEL7.1 and RHEL7.2

Version-Release number of selected component (if applicable):
tigervnc-1.2.80-0.30.20130314svn5065 defaults to -listen tcp
tigervnc-1.3.1-3.el7 defaults to -nolisten

How reproducible:


Additional info:

Details are documented in KCS article at https://access.redhat.com/solutions/2097501

This is not reflected in the man page, or the release notes.

Reassigning to xorg-x11-server, because those options (-listen/-nolisten) actually come from Xorg, which is missing upstream patch [1] mentioning this change.

[1] - https://cgit.freedesktop.org/xorg/xserver/commit/?id=8fc295bd

This really is a tigervnc bug.  xserver has had the historic listen-on-tcp behaviour restored since:

* Thu May 28 2015 Adam Jackson <ajax> 1.17.1-0.5
- Restore RHEL7 listen-on-tcp defaults

tigervnc needs to pass --enable-listen-tcp to the build phase for xserver.

Fixed in tigervnc-1.3.1-7.el7.

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