ssh-agent won't work after upgrading Ubuntu-MATE to 21.04

Adam Funk a24061 at ducksburg.com
Wed Aug 25 11:08:21 UTC 2021


Hi,

I upgraded Ubuntu-MATE from 20.10 to 21.04 yesterday morning (running
a little late, I know) and ssh-agent stopped working properly. I use
ssh keys a lot (especially for git and svn repositories) so this is
driving me nuts and interfering with my work.

Normally I log in to MATE, open a terminal, and use ssh-add to enter
the passphrases and activate several keys, then I akeep using them
freely for the time limit I set in ssh-add or until I log out.


Now I'm getting "Could not open a connection to your authentication
agent." in response to any ssh-add command.

I can get it working in *one* terminal by running this:

eval "$(ssh-agent)"

but then ssh-add commands and anything using those keys (svn up, svn
ci, git pull, git push) will only work in that same terminal, so I
have to cd all over the place when moving between different tasks and
start over if I accidentally close the magic terminal.


`grep -i ssh /var/log/syslog` turns up several repetitions of these
lines yesterday after I rebooted (after the upgrade):

sssd-ssh.socket: Bound to unit sssd.service, but unit isn't active.
Dependency failed for SSSD SSH Service responder socket.
sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'.

and these lines from when I last logged into the MATE desktop this
morning (I logged out and back in to see if that fixed it):

Listening on GnuPG cryptographic agent (ssh-agent emulation).
gpg-agent-ssh.socket: Succeeded.
Closed GnuPG cryptographic agent (ssh-agent emulation).
Listening on GnuPG cryptographic agent (ssh-agent emulation).
gpg-agent-ssh.socket: Succeeded.
Closed GnuPG cryptographic agent (ssh-agent emulation).


Any suggestions? I'm sure I haven't changed any configurations related
to this.

Thanks,
Adam





More information about the ubuntu-users mailing list