Public bug reported: gcr4 4.2.0-5 (Ubuntu Noble) ships gcr-ssh-agent.socket without setting the SSH_AUTH_SOCK environment variable. As a result, the SSH agent socket path (/run/user/1000/gcr/ssh) is not propagated to the user session, causing SSH operations to fail or fall back to stale/wrong agent sockets.
This was fixed upstream in gcr 4.2.1 via commit b12cc639: https://gitlab.gnome.org/GNOME/gcr/-/commit/b12cc639949c4b548d84625b292a2aff1faaf195 The fix adds SSH_AUTH_SOCK propagation to the gcr-ssh-agent.socket systemd unit. It should be straightforward to cherry-pick into the Noble package. Related bug: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/2061288 Ubuntu release: 24.04 LTS (Noble Numbat) Package version: gcr4 4.2.0-5 (apt-cache policy gcr4) Expected: SSH_AUTH_SOCK is set to /run/user/1000/gcr/ssh after login Actual: SSH_AUTH_SOCK is not set by gcr-ssh-agent.socket, causing SSH agent to be unreachable ** Affects: gcr4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2154799 Title: gcr4: SSH_AUTH_SOCK not set by gcr-ssh-agent.socket in Noble (fix available in upstream 4.2.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr4/+bug/2154799/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
