[Bug 383926] Re: ssh-aggent stopped accepting connections

2010-11-10 Thread David Huggins-Daines
I am seeing this bug too, since I upgraded to Maverick, but only on one of my computers (!) They are both AMD64 and running auto-login, so I'm not exactly sure what the problem is, except maybe that the one which is not working was upgraded while the one which works was a fresh install. --

[Bug 383926] Re: ssh-aggent stopped accepting connections

2010-11-10 Thread David Huggins-Daines
Well, logging out and logging back in on the non-working machine resolves the problem. I guess gnome-keyring isn't being initialized properly on auto-login? Strange because it prompts me for my login password... -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926

[Bug 383926] Re: ssh-aggent stopped accepting connections

2010-06-22 Thread Steven Winikoff
Oops, I was a bit quick on the trigger -- $SSH_AUTH_SOCK points directly to the socket, not to the directory containing it. :-( The correct workaround is as follows (i.e., this is a correction to comment #9 above): /usr/bin/gnome-keyring-daemon --start newsockdir=`ls -dt1 /tmp/keyring* | head

[Bug 383926] Re: ssh-aggent stopped accepting connections

2010-03-10 Thread Sebastien Bacher
Could you try if that's still an issue in lucid? -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list

[Bug 383926] Re: ssh-aggent stopped accepting connections

2010-03-10 Thread Marius Gedminas
I do not know how to reproduce the problem. It never happened again to me on Jaunty or on Karmic. -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh

[Bug 383926] Re: ssh-aggent stopped accepting connections

2009-06-10 Thread Sebastien Bacher
Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME) ** Changed in: gnome-keyring (Ubuntu) Importance: Undecided = Low ** Changed in:

[Bug 383926] [NEW] ssh-aggent stopped accepting connections

2009-06-05 Thread Marius Gedminas
Public bug reported: Suddenly my ssh-agent stopped accepting connections: $ ssh-add -l Could not open a connection to your authentication agent. It is still running (pid 4530, which matches the value of $SSH_AGENT_PID), but doesn't appear to be listening on the socket

[Bug 383926] Re: ssh-aggent stopped accepting connections

2009-06-05 Thread Marius Gedminas
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27524381/Dependencies.txt -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh

[Bug 383926] Re: ssh-aggent stopped accepting connections

2009-06-05 Thread Marius Gedminas
Checking a working GNOME session (on another machine) I see that normally it's gnome-keyring that's listening on socket.ssh. I don't have a gnome-keyring process running (and I don't see gnome-keyring- daemon either). Neither ~/.xsession-errors nor /var/log/* have any recent error messages from

[Bug 383926]

2009-06-05 Thread Marius Gedminas
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27526943/Dependencies.txt -- ssh-aggent stopped accepting connections https://bugs.launchpad.net/bugs/383926 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh