The problem occurs in combination with automatic login, because then the gnome-keyring is not opened automatically. So if you boot a computer with wakeonlan with automatic login, you won't be able to reach a vino- session from remote because you are not able to unlock the gnome- keyring.
The solution seems to be NOT to use gnome-keyring to store the vino- password. btw. the problem doesn't occur with a computer which was updated from Karmic! This one seems to store the password in another place (too?), so there is no need to unlock the gnome-keyring. Unfortunately I don't know where the password was stored in Karmic or which option to change in gconf-editor. It should be easy to find a workaround but I haven't found it yet. -- gnome-keyring-manager interferes with the VNC server https://bugs.launchpad.net/bugs/562423 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
