You are not logged in.
I think I found the upstream chatter regarding this issue, which points at evidence we're struggling with the change to gnome-keyring not working as expected.
https://gitlab.gnome.org/GNOME/gnome-ke … issues/140
You can then find links to attempts at change and others having the same problems and hack solutions we're having in this thread.
I don't have a problem with GNOME. I use the standard Xorg and Awesome. This is not just a GNOME problem, but a general issue with the standard ssh-agent. Maybe this was primarily described for GNOME, but not all posts! Definitely, this can't be solved only at the GNOME solution level; there's some change in OpenSSH, NetworkManager, or somewhere something significant has changed. For example, there could be an issue with resolving: `%t` in the systemd ssh-agent service?
Offline
Ftr, https://archlinux.org/packages/extra/x86_64/gcr-4/ is used exclusively by "gnome stuff"™, whatever your desktop is, you're getting that from "gnoem-stuff"™ and from your comment most likely from https://archlinux.org/packages/extra/x8 … er-applet/ (look at the url.…)
Online
I had problems with setting SSH_AUTH_SOCK on Xfce, tried setting it in `/etc/profile.d/*.sh` but it was getting overridden by something.
Here's what helped:
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false
THEN settings it in `/etc/profile.d/*.sh` worked.
Offline
I solved it by adding
export SSH_AUTH_SOCK=$XDG_RUNTIME_DIR/gcr/ssh
to
.zshrc
gcr-4 automatically setting it in socket file doesn't work.
Offline