Bug 485128

Summary:	gnome-keyring updates after 2.25.4.2-1.fc11 break ssh-add
Product:	[Fedora] Fedora	Reporter:	Tom "spot" Callaway <tcallawa>
Component:	gnome-keyring	Assignee:	Tomáš Bžatek <tbzatek>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	rawhide	CC:	mclasen, tbzatek, tsmetana, walters
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-02-13 16:30:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.