Bug 1215270

Summary: ssh-agent, pkcs#11 and gpg-agent functionality not working
Product: [Fedora] Fedora Reporter: David Woodhouse <dwmw2>
Component: gnome-keyringAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bmbouter, debarshir, dgoodwin, mclasen, mszalowicz, Per.t.Sjoholm, rbarlow, stefw, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 13:51:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1520268    

Description David Woodhouse 2015-04-24 20:48:18 UTC
Since updating to F22, I no longer seem to have a working ssh-agent, gpg-agent or gnome-keyring PKCS#11 token. It looks like gnome-keyring-daemon has been invoked with --components=secrets

Is there something that's supposed to replace the functionality for those other three things? If so, the upgrade path isn't working correctly and isn't setting them up.

Comment 1 Marcin SzaƂowicz 2015-05-27 12:52:55 UTC
this bug probably depends on bug #1225472

Comment 2 Brian Bouterse 2015-08-17 16:06:32 UTC
I really with this was fixed.

Comment 3 Fedora End Of Life 2016-07-19 13:51:47 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.