Description of problem: When I click in vino-preferences the option "Allow other users to view your desktop", it says that "[...] Others can access your computer using the address localhost". vino-server is not running. Not very usefull when away from localhost. If I launch on a command line: $ /usr/libexec/vino-server 05/07/2011 12:28:44 PM Autoprobing TCP port in (all) network interface 05/07/2011 12:28:44 PM Listening IPv6://[::]:5900 05/07/2011 12:28:44 PM Listening IPv4://0.0.0.0:5900 05/07/2011 12:28:44 PM Autoprobing selected port 5900 05/07/2011 12:28:44 PM Advertising authentication type: 'VNC Authentication' (2) 05/07/2011 12:28:44 PM Advertising security type: 'VNC Authentication' (2) vino-preferences says : "[...] Others can access your computer using the address 10.0.21.200 or mypc.local" Then I can access to that pc remotely. But if I uncheck option "Allow other users to view your desktop", vino-server stops and if I check it again, vino-server does not start. Version-Release number of selected component (if applicable): vino-2.32.2-1.fc14.x86_64 How reproducible: every time Steps to Reproduce: 1. ps axf|grep vino --> nothing 2. run /usr/libexec/vino-server 3. ps axf|grep vino 19124 pts/2 Sl 0:00 | | \_ /usr/libexec/vino-server you can access to remote pc via vnc. 4. uncheck option "Allow other users to view your desktop", vino-server is stopped. 5. Recheck that option, vnc-server does not start. Cannot access to remote server. Actual results: Cannot access to remote server just by clicking option "Allow other users to view your desktop". Expected results: I expect that vino-server would start after clicking that option, so I can access to my remote pc. Additional info:
Perhaps relevant in ~/.xsession-errors? gnome-session[29643]: WARNING: Failed to start app: Unable to start application: Failed to execute child process "vino-server" (No such file or directory)
nothing in that file.
Continuing to see this in Fedora 16. Any workaround? Any plans to fix?
~/.config/gnome-session/saved-session/vino-server.desktop has this in it: Exec=vino-server --sm-client-id 107cebc82657a6e82c131931020461053200000138960038 The file was recently saved, so it appears that when vino saves its state on shutdown, it's not saving a full path even though it should be.
(In reply to comment #4) > ~/.config/gnome-session/saved-session/vino-server.desktop has this in it: > > > Exec=vino-server --sm-client-id > 107cebc82657a6e82c131931020461053200000138960038 > > The file was recently saved, so it appears that when vino saves its state on > shutdown, it's not saving a full path even though it should be. I'm getting this very same problem on Fedora 16 with all stable updates.
(In reply to comment #5) I am seeing the same thing in Fedora 17 with all updates. I have to start /usr/libexec/vino-server manually. Mentioned file ~/.config/gnome-session/saved-session/vino-server.desktop does not even exist on my system and I had the vino-server running, preferences set correctly in the GUI for vino-preferences and I correctly logged out from Gnome.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping