Remote Desktop asks for keyring login on remote end

Bug #655433 reported by Martin Meyer
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
vino (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: vino

I have one Maverick system trying to connect to another by remote desktop (VNC). The remote server is connected to my TV, so I've set it up to automatically login to Gnome. I have used the following settings for Vino on the server/HTPC:
* Require a password for VNC login,
* Don't require confirmation before others take remote control,

The problem is, when I try to connect to that server from my laptop, it prompts the server's console (connected to my TV) on the remote server for the GNOME keyring password. It's not supposed to do that, I told it not to require confirmation before allowing remote users to take over!

Subsequent connections to the VNC service do not prompt a password. Previous releases of Ubuntu did not behave this way, I was simply able to log in after boot.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: vino 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Tue Oct 5 20:37:09 2010
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: vino

Revision history for this message
Martin Meyer (elreydetodo) wrote :
Revision history for this message
aa2k (murilla1) wrote :

Not sure if this will help you.
I have 2 systems, my laptop does not use autologin and Remote desktop (VNC) worked out of the box as soon as I entered the password for it when I enabled it, etc.

My desktop has autologin enabled and I had problem trying to make it work same way you described, I ended up getting rid of keyring for good, in my case I dont need this on my desktop so as soon as I got rid of it it worked just fine..

Before you disable keyring you should try entering a a blank password when asked by keyring (when you are setting up the password for remote desktop it will pop up and ask you for the keyring password, here just leave it blank, 50% chance this will work...
if not, the last resort is killing keyring thing...

There are 3 services you need to disable (this services all the gnome-keyring-daemon files):
go to System > Preferences > Startup application, look for these 3 and disable and remove them from the list...
certificate of key storage
Secret Storage Service
SSH key agent

Once this is done delete the 2 following files:
/usr/bin/gnome-keyring-daemon
/usr/bin/gnome-keyring

reboot and you should be fine now, you may need to enter the password one more last time on remote desktop setup first after you reboot since it me be deleted when you delete the keyring files.

Good luck...

Revision history for this message
mredude (mr-e-dude-420) wrote :

My solution to this problem was unique and original. YAY!!! After trying everyone elses solution and just making the gnome desktop worse, I finally discovered that it was vino-server that was loading the gnome-keyring password prompt thing. Not a function of the gnome-keyring itself. So I went to http://ftp.gnome.org/pub/GNOME/sources/vino/2.32/ and got the source code to vino and compiled it with the ./configure --disable-gnome-keyring switch. I hoped I spelled all that right. a ./configure --help | list will list the correct switch to use. But it says --enable and not --disable but disable works. But I had to install the gnome-keyring-1 development libraries anyway even though it didn't use them. So anyways after I compiled vino and installed it, oh yeah, even though I did a make install the vino-server binary didn't get installed. A fight to the bitter end. So I had to manually copy that out of the source directory and I choose to put it into /usr/local/lib dir and make a symbolic link from the old vino-server, locate vino-server will tell ya where it is, something like /usr/lib/vino I think, to the new vino-sever. Rebooted. Had to turn remote desktop on again, and... and...

IT WORKED!!! No gnome-keyring password prompt when I log in with vnc to my :0 desktop.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.