Bug 475724 - vino does not honour alternate port setting
vino does not honour alternate port setting
Product: Fedora
Classification: Fedora
Component: vino (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Søren Sandmann Pedersen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-10 00:24 EST by Michael Cronenworth
Modified: 2014-06-18 05:10 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:14:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Cronenworth 2008-12-10 00:24:53 EST
Description of problem: When setting up vino using the "Remote Desktop" menu item, I set a port (56102 for example) instead of 5900. When I turn vino off and back on, vino is still listening on 5900. Nothing is listening on 56102. If I log out and back in it's the same result. I verified in gconf-editor that the "alternative_port" key is set to 56102 and the "use_alternative_port" key is checked. Still on port 5900.

Version-Release number of selected component (if applicable): vino-2.24.1-1.fc10.x86_64

How reproducible: Always

Steps to Reproduce:
1. Check "Allow other users to view your desktop"
2. On Advanced tab, check "Use an alternative port:" and enter 56102.
3. On General tab, uncheck and recheck "Allow other users to view desktop" or logout and back in.
Actual results: vino is listening on port 5900

Expected results: vin is listening on port 56102

Additional info: i386 and x86_64 arches are both affected.
Comment 1 Bug Zapper 2009-11-18 05:24:59 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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: 
Comment 2 Michael Cronenworth 2009-11-18 10:20:49 EST
I'm not sure how to continue with this bug. Starting with F11 and F12, the ability to set an alternate port was taken away.
Comment 3 Bug Zapper 2009-12-18 02:14:13 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.

Note You need to log in before you can comment on or make changes to this bug.