Bug 1248179

Summary:	gnome-keyring version <3.16.0-3 breaks opengpg smartcard device functionality
Product:	[Fedora] Fedora	Reporter:	Ricky Burgin <ricky>
Component:	gnome-keyring	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	22	CC:	debarshir, mclasen, stefw, walters
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 19:54:02 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:

Description Ricky Burgin 2015-07-29 19:36:07 UTC

Description of problem:

Adequately described on the Debian bugtracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773304


Version-Release number of selected component (if applicable):
3.16.0-1.fc22

How reproducible:
100%

Steps to Reproduce:
1. Insert openpgp smart card (in my case, a YubiKey NEO)
2. Open terminal, type gpg --card-status
3. Experience mild disappointment and frustration

Actual results:
[rburgin@Ricky-PC ~]$ gpg --card-status
gpg: pcsc_establish_context failed: no service (0x8010001d)
gpg: card reader not available
gpg: OpenPGP card not available: general error

Expected results:
The status of my card

Additional info:

Comment 1 Stef Walter 2015-08-03 07:56:44 UTC

gnome-keyring 3.17.4 (and thus 3.18.x) no longer has a gpg-agent. The upstream gnupg2 agent is used instead. This bug will be fixed at that point.

Comment 2 Ricky Burgin 2015-08-03 12:57:10 UTC

Thanks Stef, how best can I work around this until a >=3.17.4 release reaches Fedora updates/updates-testing? Any idea when to expect that to happen?

Comment 3 Mike McCune 2016-03-28 23:03:07 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 4 Fedora End Of Life 2016-07-19 19:54:02 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.