Red Hat Bugzilla – Bug 611555
vncserver starting at boot with vino produces confusing results for users
Last modified: 2014-06-18 05:13:15 EDT
Description of problem:
If vncserver is chkconfig'd on at boot time (to start say on :1) and the user it's run as has a vino set to start (has desktop sharing ticked) in their config, then vino will start listening on 5900 for connections to this VNC session (as well as the native VNC server port on 5901 provided by vncserver/Xvnc).
When the user logs into the console they assume their :0 X session will be on the :0 VNC session (but it isn't) it's on port 5902 (:2 vnc session). This leads to confusion.
Should vino-server start at all (or at least be an option) for Xvnc servers, given it's already providing VNC?
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.
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 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.
Thank you for reporting this bug and we are sorry it could not be fixed.