Bug 970841

Summary: vncviewer -listen permits only one connection
Product: [Fedora] Fedora Reporter: Jason Tibbitts <j>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: bphinz, jgrulich, twaugh, xgl-maint
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 12:39:11 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 Jason Tibbitts 2013-06-05 04:18:06 UTC
In F17, vncviewer -listen would sit around, accepting multiple simultaneous connections until you killed it.  In F18, it only appears to accept one connection and exits when it closes.

I know that the -listen functionality has been the subject of some drama lately, but pretty much the only thing I used it for was so that I could kickstart a bunch of machines (with the vnc --host kickstart option) and watch their progress.  That doesn't appear to work well now; the first connection attempt will work, but successive ones won't.  Obviously I need to find a better way to monitor my kickstart installs, but I figured it would be nice to at least get it on the record that this regressed.

Comment 1 Fedora End Of Life 2013-12-21 13:52:10 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2014-02-05 21:40:52 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Jason Tibbitts 2016-01-27 03:06:54 UTC
Sadly, vncviewer -listen in Fedora 23 still does not accept more than one connection.  I was doing some searching to see if perhaps it was fixed in some newer version or if there was a patch, but all I found was this old bug.  Might as well reopen it.

To recap, vncviewer -listen used to (in Fedora 17, before Fedora switched to tigervnc) accept multiple connections.  By running vncviewer -listen once, I could have a whole bunch of clients (in this case, machines being installed via kickstart) connect at once.  Now it only accepts one connection, and I have to run another vncviewer in order for it to accept anything else.

I have a poor workaround (loop calling netstat to see if something is listening on 5500) but...

Comment 4 Jan Grulich 2016-05-23 16:53:23 UTC
The "-listen" parameter comes from the X server, which means that if anything has changed, then I assume it was there and not in tigervnc.

Comment 5 Fedora End Of Life 2016-11-24 10:59:27 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2016-12-20 12:39:11 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.