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.
--
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
I've seen exactly the same symptoms with Karmic and now also with Lucid.
Apparently what happens is that gnome-keyring-daemon starts correctly at
the beginning of a new session, but eventually exits silently. This
happened to me today in the session from which I'm typing this; gnome-
I don't have a fix for this problem, but I did just find a workaround:
1) start gnome-keyring-daemon manually; e.g., from a shell prompt,
type
/usr/bin/gnome-keyring-daemon --start
2) assuming that $SSH_AUTH_SOCK is pointing to the socket created by
the old (now defunct)
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
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
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
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
Desktop Bugs, which is a bug assignee.
--
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:
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
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: gnome-keyring 2.26.1-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=lt_LT.UTF-8
LC_CTYPE=lt_LT.UTF-8
Uname: Linux 2.6.28-12-generic i686
UserGroups: adm admin audio cdrom davfs2 dialout dip floppy
** 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
Desktop Bugs, which is subscribed to
11 matches
Mail list logo
