> (2) It does not appear that xfce launches applications as transient systemd user units. To see this, try > running the following from a terminal in a graphical session:
That's not necessary, provided that the graphical shell process has the environment set and exports it when forking to the app process. > (3) So, given that we moved from gnome-keyring to gcr4, my guess is that gnome-keyring had another method of setting the SSH_AUTH_SOCK variable in addition to the systemctl --user set-environment call in the socket unit, and that gcr4 has no such mechanism. Ok, xfce4-session has special integration with gnome-keyring-daemon. It runs `gnome-keyring-daemon` which prints out some key-value-pairs to stdout and xfce4-session uses those to set its own environment: $ gnome-keyring-daemon --start 2>/dev/null GNOME_KEYRING_CONTROL=/run/user/1000/keyring SSH_AUTH_SOCK=/run/user/1000/keyring/ssh See https://salsa.debian.org/xfce- team/desktop/xfce4-session/-/blob/972de48270971c2dc872bb5608ddac4a9ad8e0a1/xfce4-session/xfsm- compat-gnome.c#L158 Now that gnome-keyring-daemon no longer provides an ssh agent, xfce4-session doesn't know where to find one anymore. I suggest a small patch to xfce4-session to try and find other known sockets, in order: $XDG_RUNTIME_DIR/gcr/ssh $XDG_RUNTIME_DIR/openssh_agent Long-term, xfce4-session should invest in moving its session startup to be systemd-based. But that's definitely out of scope for 25.10 ** Changed in: gcr4 (Ubuntu) Status: New => Won't Fix ** Changed in: gcr4 (Ubuntu) Milestone: ubuntu-25.10 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2125549 Title: ssh agent no longer work a questing upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr4/+bug/2125549/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
