Bug 485128 - gnome-keyring updates after 2.25.4.2-1.fc11 break ssh-add
Summary: gnome-keyring updates after 2.25.4.2-1.fc11 break ssh-add
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: rawhide
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-11 18:55 UTC by Tom "spot" Callaway
Modified: 2015-03-03 22:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-13 16:30:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tom "spot" Callaway 2009-02-11 18:55:11 UTC
In my .bash_profile, I have:

SSHAGENT=/usr/bin/ssh-agent
SSHAGENTARGS="-s"
if [ -z "$SSH_AUTH_SOCK" -a -x "$SSHAGENT" ]; then
   eval `$SSHAGENT $SSHAGENTARGS`
   trap "kill $SSH_AGENT_PID" 0
fi

When I login to GNOME, I open an gnome-terminal and run "ssh-add", then type in my passphrase. This has worked for several Fedora releases, to save me the time and loss of sanity that typing my passphrase 400 times costs.

With all rawhide updates of gnome-keyring after 2.25.4.2-1.fc11, ssh-add no longer works. It says things about being unable to connect to the daemon.

I've tried gnome-keyring-2.25.90-4.fc11 and gnome-keyring-2.25.5-1.fc11. Only by downgrading to 2.25.4.2-1.fc11 can I restore the expected behavior.

Comment 1 Matthias Clasen 2009-02-12 15:24:38 UTC
Is gnome-keyring-daemon not getting started, or does it crash ?

Comment 2 Tom "spot" Callaway 2009-02-13 16:30:54 UTC
Well, I thought it was crashing, so I updated to gnome-keyring-2.25.90-4.fc11.x86_64 and rebooted... of course, it doesn't fail like it was before. 

If I can reproduce this, I'll reopen it, but it seems to be working fine now.


Note You need to log in before you can comment on or make changes to this bug.