Bug 1225472

Summary:	/run/user/<uid>keyring directory is missing while keyring is running
Product:	[Fedora] Fedora	Reporter:	Marcin Szałowicz <mszalowicz>
Component:	gnome-keyring	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	andrew, bmbouter, debarshir, dgoodwin, mclasen, 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 14:17:20 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 Marcin Szałowicz 2015-05-27 12:52:23 UTC

Description of problem:
according to GPG_AGENT_INFO and SSH_AUTH_SOCK keyring should be available by /run/user/<uid>/keyring while the directory is missing

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

How reproducible:
Install fresh Fedora22, and check GPG_AGENT_INFO or SSH_AUTH_SOCK and see those are pointing to non-existing directory

Steps to Reproduce:
1. install fresh fedora 22
2. start fedora 22 
3. open terminal
4. issue: ls $GPG_AGENT_INFO or ls $SSH_AUTH_SOCK and observe the error

Actual results:
directory /run/user/<uid>/keyring is missing

Expected results:
directory /run/user/<uid>/keyring shouldn't be missing

Additional info:

Comment 1 Brian Bouterse 2015-08-17 16:06:54 UTC

I really with this was fixed so that 1215270 could also be fixed.

Comment 2 Andrew Cowie 2015-11-30 23:37:01 UTC

On Fedora 23 I have that directory but GPG_AGENT_INFO is no longer set, and there is no /run/user/$uid/keyring/gpg (or whatever) alongside pkcs11 and ssh.

AfC

Comment 3 Fedora End Of Life 2016-07-19 14:17:20 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.