[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2010-09-16 Thread Bug Watch Updater
** Changed in: gnome-keyring Status: Invalid => Expired ** Changed in: gnome-keyring Importance: Unknown => Medium -- seahorse-agent not invoked for second ssh key https://bugs.launchpad.net/bugs/195908 You received this bug notification because you are a member of Ubuntu Desktop Bugs,

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-12-03 Thread Albéric de Pertat
To complete on the first point of the initial post (what keys are "seen" by seahorse), what i've found (it's hidden somewhere on the seahorse pages at live.gnome.org) is that seahorse will only take into account keys beginning with id_rsa or id_dsa I was using a key named id_vpn in my .ssh folder

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-11-20 Thread Richard Laager
** Changed in: gnome-keyring (Ubuntu) Status: Triaged => Invalid -- seahorse-agent not invoked for second ssh key https://bugs.launchpad.net/bugs/195908 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing li

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-11-20 Thread Gustavo Gama
I was doing the same as you: ~/.gnome2/keystore had symlinks to ~/.ssh, as was suggested by Live Gnome's page (I think those instructions are gone now, btw). Anyway, your suggestion to remove ~/.gnome2/keystore was spot-on; the ssh keys are once again managed by the keyring as expected. Thanks a

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-11-20 Thread Richard Laager
Hmm, that might explain why I'm working all of a sudden. I removed my ~/.gnome2/keystore directory since it wasn't working. You might want to try that. My ~/.gnome2/keyring was symlinks to ~/.ssh. It sounds like you're doing it the other way around, so, in your case, make sure you copy the real ke

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-11-20 Thread Gustavo Gama
No. I don't even have a ~/Private dir. But I have symlinks from ~/.ssh/id_rsa_XXX to ~/.gnome2/keystore/. -- seahorse-agent not invoked for second ssh key https://bugs.launchpad.net/bugs/195908 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assi

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-11-20 Thread Richard Laager
Well, this is certainly bizarre. It's started working for me in the last couple of days. It's definitely working for me on this boot. I'll see if it breaks again. It may be a race condition somewhere, especially since my ~/.ssh is symlinked to my ~/Private. Gustavo, do you have your ~/.ssh symlink

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-11-19 Thread Gustavo Gama
Same here. Worked fine in Hardy and it seems to be broken in Intrepid. -- seahorse-agent not invoked for second ssh key https://bugs.launchpad.net/bugs/195908 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing lis

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-11-14 Thread Richard Laager
I'm running Intrepid and having the same issue. The work-around no longer works for me, nor for this person: https://lists.ubuntu.com/archives/ubuntu-users/2008-October/162455.html -- seahorse-agent not invoked for second ssh key https://bugs.launchpad.net/bugs/195908 You received this bug notifi

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-04-29 Thread Sebastien Bacher
not a seahorse issue, the gnome-keyring agent is used in hardy ** Changed in: seahorse (Ubuntu) Importance: Undecided => Low Status: New => Invalid -- seahorse-agent not invoked for second ssh key https://bugs.launchpad.net/bugs/195908 You received this bug notification because you are

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-04-28 Thread Bug Watch Updater
** Changed in: gnome-keyring Status: Unknown => Invalid -- seahorse-agent not invoked for second ssh key https://bugs.launchpad.net/bugs/195908 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list deskto

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-04-12 Thread Mario Manno
The solution described in http://live.gnome.org/GnomeKeyring/Ssh works for me. Running the following shell script made all my ssh keys usable again: mkdir ~/.gnome2/keystore; for i in ~/.ssh/*pub; do key=$(basename $i .pub); echo -e "[default]\npurposes=ssh-authentication" > ~/.gnome2/keyst

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-04-11 Thread Sebastien Bacher
Thank you for your bug, that's known upstream, http://bugzilla.gnome.org/show_bug.cgi?id=524454 ** Changed in: gnome-keyring (Ubuntu) Importance: Undecided => Low Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs) Status: New => Triaged ** Also affects: gnome-keyring via

[Bug 195908] Re: seahorse-agent not invoked for second ssh key

2008-04-10 Thread Mario Manno
** Changed in: gnome-keyring (Ubuntu) Sourcepackagename: seahorse => gnome-keyring -- seahorse-agent not invoked for second ssh key https://bugs.launchpad.net/bugs/195908 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ub