Bug 1765552

Summary: duplicate ssh-agents running
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 30CC: caillon+fedoraproject, gnome-sig, john.j5live, mclasen, rhughes, rstrode, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-26 17:39:25 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 Brian J. Murrell 2019-10-25 11:54:47 UTC 
Description of problem:
I have two ssh-agents running:
$ ps -ef | grep ssh-agent
brian    23366 23128  0 07:25 ?        00:00:00 /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "/usr/bin/gnome-session"
brian    24807 23067  0 07:25 ?        00:00:00 /usr/bin/ssh-agent -D -a /run/user/1001/keyring/.ssh

Version-Release number of selected component (if applicable):
gnome-session-3.32.0-1.fc30.x86_64

One is started by gnome-session:

23128 tty2     Sl+    0:00          \_ /usr/libexec/gnome-session-binary
23366 ?        Ss     0:00              \_ /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "/usr/bin/gnome-session"

and the other by gnome-keyring-daemon:

23067 ?        SLl    0:01 /usr/bin/gnome-keyring-daemon --daemonize --login
24807 ?        S      0:00  \_ /usr/bin/ssh-agent -D -a /run/user/1001/keyring/.ssh

The one that is actually being used is:
$ echo $SSH_AUTH_SOCK
/run/user/1001/keyring/ssh
$ sudo fuser /run/user/1001/keyring/ssh
/run/user/1001/keyring/ssh: 23067

Which is the one from gnome-keyring-daemon.  So why is gnome-session starting one and how do I disable that?  It seems that the GNOME startup ought to figure that all out for me and only start one.
Comment 1 Ben Cotton 2020-04-30 20:52:41 UTC 
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Ben Cotton 2020-05-26 17:39:25 UTC 
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.