Bug 1378922

Summary: tigervnc-server needs to be rebuilt to re-enable listen-on-tcp behavior in RHEL 6.8
Product: Red Hat Enterprise Linux 6 Reporter: amit yadav <ayadav>
Component: tigervncAssignee: Jan Grulich <jgrulich>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.8CC: aronparsons, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-21 09:52:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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