This is a SRU (Stable Release Update) request to backport the upstream fix to Ubuntu Noble (24.04 LTS).
[Impact] gcr4 4.2.0-5 in Ubuntu Noble ships gcr-ssh-agent.socket without setting the SSH_AUTH_SOCK environment variable. Users who rely on gcr-sw-agent as their SSH agent find that SSH operations fail silently or fall back to stale/wrong agent sockets after login, because the correct socket path (/run/user/1000/gcr/ssh) is never propagated to the user session. [Fix] Upstream fixed this 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. This is a minimal, self-contained change that can be cherry-picked into the Noble package as gcr4 4.2.0-5ubuntu0.1. [Test Plan] 1. On Ubuntu 24.04 Noble, log in to a GNOME session. 2. Run: echo $SSH_AUTH_SOCK Expected (before fix): empty or pointing to wrong path (e.g. /run/user/1000/keyring/ssh) Expected (after fix): /run/user/1000/gcr/ssh 3. Run: ssh-add -l Expected (after fix): lists loaded keys without "Connection refused" [Where problems could occur] The change only modifies the gcr-ssh-agent.socket systemd unit to propagate SSH_AUTH_SOCK. Risk of regression is low. Users who use gpg-agent or openssh's ssh-agent as their SSH agent instead of gcr-ssh-agent are unaffected. [Other Info] Related bug: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2061288 Upstream fix: https://gitlab.gnome.org/GNOME/gcr/-/commit/b12cc639949c4b548d84625b292a2aff1faaf195 -- 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
