https://bugzilla.redhat.com/show_bug.cgi?id=1436961
David Gibson <dgibson(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|25 |26
Flags| |needinfo?(petersen(a)redhat.c
| |om)
--- Comment #7 from David Gibson <dgibson(a)redhat.com> ---
The problem is, alas, worse in Fedora 26. Now, ssh agent doesn't work from any
programs.
I have, however, been able to track down the problem a bit further.
Initially, xmonad-mate was starting up with gnome-keyring. I think the ssh
agent included in gnome-keyring was working - except that it doesn't do what I
need because of bug 1248916.
I disable the gnome-keyring ssh component in autostart, and now ssh-agent is
started as well as gnome-keyring. Unfortunately, SSH_AUTH_SOCK is still
pointed at gnome-keyring, instead of ssh-agent, hence the breakage.
I did notice that in the tree of processes under lightdm, there are two notable
subtrees - things under the xmonad process (including terminals started with
alt-shift-enter) and things under the mate-session process (things started from
menus).
My guess is that in F25 (where, again, both ssh-agent and gnome-keyring were
started) the things under xmonad had SSH_AUTH_SOCK set to ssh-agent, and those
under mate-session pointed at gnome-keyring.
Now, under F26, they're at least consistent - fixing bug 1413338, but always
point at gnome-keyring, even when they shouldn't.
--
You are receiving this mail because:
You are on the CC list for the bug.