Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1593276

Summary: gnome-keyring-daemon eating 100% cpu
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: gnome-keyringAssignee: David King <dking>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: jacob.e.keller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-05 15:43:08 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:
Attachments:
Description Flags
gnome-keyring-daemon backtrace 1
none
gnome-keyring-daemon backtrace 2 (100% CPU user) none

Comment 2 Jacob Keller 2018-06-25 22:25:02 UTC
Created attachment 1454510 [details]
gnome-keyring-daemon backtrace 1

Comment 3 Jacob Keller 2018-06-25 22:25:33 UTC
Created attachment 1454511 [details]
gnome-keyring-daemon backtrace 2 (100% CPU user)

I see this happen as well, sometimes multiple gnome-keyring-daemons get launched for some reason, and it's the 2nd one which consumes 100% CPU. This also seems to be causing ssh to be unable to obtain keys.

I've attached full backtraces of the running gnome keyring daeomon processes.

Comment 4 Jacob Keller 2018-10-05 15:43:08 UTC
This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1636330

It appears because the pam_gnome_keyring.so fails to identify the XDG_RUNTIME_DIR, and launches multiple gnome-keyring-daemon instances

*** This bug has been marked as a duplicate of bug 1636330 ***