Hit this issue today trying to enable vino from a remote ssh terminal. Took me half a day to figure out that the server side popped up the keyring window causing TightVnc client to hang during authentication. Sad :(
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/562423 Title: gnome-keyring-manager interferes with the VNC server Status in GNOME Remote Desktop: New Status in vino package in Ubuntu: Confirmed Bug description: Binary package hint: vino Actual configuration PC A : Ubuntu Lucid Lynx (upgraded from an updated 09.10) with distant desktop enabled PC B : Another OS with vncviewer After the first start of PC A, if I launch vncviewer on PC B with correct login/password to view the PC A desktop, vncviewer waits for the connection acceptation. I have to go to the PC A and enter my user password in the "gnome-keyring-manager" window that appeared after the first connect attempt of PC B. After password acceptation, PC B vncviewer is able to connect/disconnect without any problems. Why vncserver needs my user password to know it's own password ? To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/562423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
