-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-7.8
-
None
-
Important
-
5
-
rhel-sst-display-desktop-foundation
-
ssg_display
-
None
-
False
-
-
None
-
DESKTOP Cycle #1 10.beta phase, DESKTOP Cycle #3 10.beta phase, DESKTOP Cycle #4 10.beta phase, DESKTOP Cycle #5 10.beta phase, DESKTOP Cycle #2 10.beta phase
-
None
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
Description of problem:
gnome-keyring-daemon hangs and eats 100% CPU when creating a new VNC session. SSH connections from the system to another system also hang as gnome-keyring-daemon has a lock on ssh keys via the pam stack. There is already a bugzilla for this issue mark "CLOSED EOL". However, the fix is not implemented in the current (above) version of gnome-keyring daemon. According to the forums, this fix is in gnome-keyring-3.31.90+. RHEL 7.7 - 7.8 does not include 3.31.90.
Version-Release number of selected component (if applicable):
gnome-keyring-3.28.2-1.el7.x86_64
gnome-keyring-pam-3.28.2-1.el7.x86_64
Actual results:
gnome-keyring is not terminating the old daemon when starting a new one which causes 100% CPU utilization and ssh hangs via pam stack.
Expected results:
gnome-keyring is to only start one process and if a new process needs to be started, the previous one is to be terminated.
- relates to
-
RHEL-25560 gnome-keyring-daemon hangs and pins one CPU core if SSH agent fails to start
- Closed
- external trackers