Bug 1043324

vino package should require control-center as it needs it to function.

Even after installing control-center (sigh and a bunch of gnome dependency stuff) I still don't have vino-preferences.  Has the functionality moved into control-center depreciating vino-preferences?

Running F20 Xfce desktop.

(In reply to Andy Lawrence from comment #2)
> Even after installing control-center (sigh and a bunch of gnome dependency
> stuff) I still don't have vino-preferences.  Has the functionality moved
> into control-center depreciating vino-preferences?
> 
> Running F20 Xfce desktop.

I believe they called is sharing


gnome-control-center sharing



https://git.gnome.org/browse/gnome-control-center/tree/panels/sharing?h=gnome-3-10&id=f1d52d7b3fc7da8912d0b66c40e1687e9e0ff264

These instructions seem to work on Fedora 20. Does not work on Fedora 19.

After you have 'yum install vino' and 'yum install control-center'

You should see 'vino-server if you do 'ps ax | grep vino'

If not, then 'yum remove vino' and reinstall.

-----

Then 'yum install dconf-editor'

Then, while logged in as the user you wish to log in remotely (NOT root) do:

dconf-editor

Navigage to org/gnome/desktop/remote-access using the menu on the left side of the dconf-editor window.

What I have done here is change authentication-methods to ['vnc']

put checkmarks in:

enabled
notify-on-connect

and change the vnc-password to a base64 encoded version of the password you wish to use to log into your desktop. This password does not have to be your login password.

exit dconf-editor

Then fire up a vnc client and try to log in with your new password.

It wouldn't hurt to reboot after the dconf-editor step.

There also appears to be a lack of dependency information in the vino package.

I have been experimenting on 3 different Fedora 20 systems this afternoon. One of them was recently upgraded to 20 from 19 and was relatively virgin. The vino-server was not working on this system.

In addition to the install vino and the install control-center, you might also do 'yum install orca'. I say this because when I did a 'yum remove vino' on one system, it also wanted to remove control-center and orca.

When I then reinstalled vino, it didn't want control-center or orca.

Just to be safe, I reinstalled both of those.

-----

As a test, once you think you have everything installed and configured with dconf-editor, do a 'ps ax | grep vino' You must see a '/usr/libexec/vino-server' If not then do 'sudo shutdown -r now'

When it comes back up, again test to see vino-server in your ps ax output.

If you still do not see vino-server, go back into dconf-editor and check that the 'enabled' box is checked. Then check all of the other boxes. Encryption should be off, password should be changed to your favorite (passed through base64). Look for other boxes that had been unknowingly checked when they should be unchecked - dconf-editor seems not so faithful..

And reboot again.  I now have all 3 of my Fedora 20 systems so they respond to a remote vnc client.

A few hours ago I did a 'yum update' and a 'shutdown -r now' on 3 different Fedora 20 systems.

Each of them came up not running /usr/libexec/vino-server

I went to the console terminal, logged in as the regular user (not root) and went through the dconf-editor configuration of the /org/gnome/desktop/remote-access (no changes were made, the settings were as noted above in Comment #6).

When I exited the dconf-editor, the /usr/libexec/vino-server was now running and it was now possible to log in from a remote computer.

Curious.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.

(In reply to Fedora End Of Life from comment #9)
> ...

Haven't tried Fedora 22 yet, but I'm affected with Fedora 21. Unfortunately it looks like I'm not allowed to change

(In reply to Woi from comment #10)
> (In reply to Fedora End Of Life from comment #9)
> > ...
> 
> Haven't tried Fedora 22 yet, but I'm affected with Fedora 21. Unfortunately
> it looks like I'm not allowed to change the version

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.