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 1378922 - tigervnc-server needs to be rebuilt to re-enable listen-on-tcp behavior in RHEL 6.8
Summary: tigervnc-server needs to be rebuilt to re-enable listen-on-tcp behavior in RH...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: tigervnc
Version: 6.8
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 14:04 UTC by amit yadav
Modified: 2020-04-15 14:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 09:52:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2651841 0 None None None 2016-09-23 14:30:53 UTC
Red Hat Product Errata RHSA-2017:0630 0 normal SHIPPED_LIVE Moderate: tigervnc security and bug fix update 2017-03-21 12:29:39 UTC

Description amit yadav 2016-09-23 14:04:04 UTC 
Description of problem:
When we configure Xvnc server, it by default listen for connections for a VNC client on TCP ports 5800+x, 5900+x, and 6000+x. If I update tigervnc-server package to tigervnc-server-1.1.0-18.el6.x86_64, it stops listening on 6000+x TCP port. Which was not the default behavior with tigervnc-server-1.1.0-16.el6.x86_64.

Version-Release number of selected component (if applicable):
tigervnc-server-1.1.0-18.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install tigervnc-server-1.1.0-16.el6.x86_64 package and run Xvnc server on RHEL6 system and check if system is listening on TCP port 60XX: 

 # vncserver :99

 # ss -nlt
 State       Recv-Q Send-Q    Local Address:Port  Peer Address:Port 
 LISTEN      0      128       *:59977             *:*     
 LISTEN      0      50        *:9102              *:*     
 LISTEN      0      5         *:5999              *:*     
 LISTEN      0      64        *:40175             *:*     
 LISTEN      0      128       *:111               *:*     
 LISTEN      0      128       *:6099              *:*    <<=====  
 LISTEN      0      128       *:22                *:*

2. Stop Xvnc server and update tigervnc-server to tigervnc-server-1.1.0-18.el6.x86_64 

 $ vncserver -kill :99
 # yum update tigervnc-server

3. Restart Xvnc process and check TCP port 60XX status:

 $ vncserver :99

 $ ss -nlt
 State       Recv-Q    Send-Q   Local Address:Port   Peer Address:Port 
 LISTEN      0         128      *:59977              *:*     
 LISTEN      0          50      *:9102               *:*     
 LISTEN      0           5      *:5999               *:*     
 LISTEN      0          64      *:40175              *:*     
 LISTEN      0         128      *:111                *:*     
 LISTEN      0         128      *:22                 *:*    

Actual results:
After updating tigervnc-server-1.1.0-18.el6.x86_64, it stops listening on 6000+x TCP port. 

Expected results:
It should listen on 6000+x TCP port. 

Additional info:
Same issue was reported for RHEL7 and being tracked in following bugzilla:

 https://bugzilla.redhat.com/show_bug.cgi?id=1304646
Comment 3 Jan Grulich 2016-09-29 08:14:43 UTC 
Fixed in tigervnc-1.1.0-19.el6.
Comment 7 errata-xmlrpc 2017-03-21 09:52:56 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/RHSA-2017-0630.html
Note You need to log in before you can comment on or make changes to this bug.