I'm not sure ssh-agent.socket is at all related here. On a desktop system like Xubuntu you were probably using the gnome-keyring ssh agent (at $XDG_RUNTIME_DIR/keyring/ssh). In questing that was replaced by the gcr4 ssh agent (at $XDG_RUNTIME_DIR/gcr4/ssh), managed by /usr/lib/systemd/user/gcr4-ssh-agent.socket. Both gnome-keyring and gcr4-ssh-agent use `systemctl --user set-environment` to expose the socket path.
`systemctl --user set-environment` affects the environment of all units started after that call. If the systemd startup sequence of your desktop is correct, the desktop shell will be started *after* the gcr4-ssh- agent.socket so that the shell will get SSH_AUTH_SOCK set and it will correctly pass it to its children apps. -- 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/openssh/+bug/2125549/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
