[SOLVED] Another GTK3.20 Problem: SSH_AUTH_SOCK not set

rlees85 · 2016-04-11 10:35:06

Edit: A recent Cinnamon upgrade fixed this.

Since the weekends updates the SSH_AUTH_SOCK variable is no longer set automatically, breaking the ssh-agent.

My configuration:

- Cinnamon
- Lightdm
- Gnome-Terminal (although the other TTYs do not work either, Remmina also does not work anymore, so seems unlikely to be gnome-terminal issue)
- Gnome-Keyring

What I found:

Gnome-Keyring is starting and opening up the ssh agent unix socket correctly. When manually setting SSH_AUTH_SOCK the agent works.

Can anyone else with gnome-keyring installed do the following:

ssh-add -l

If it says:

Could not open a connection to your authentication agent.

You have the same problem.

Can you reply with:

Your desktop environment (Gnome-Shell, Cinnamon) not interested in non-GTK3 stuff like KDE as this only broken today after the upgrades.
Your login manager (ie, lightdm, gdm)
If or not your ssh-agent is also broken

Appreciate the help !

Last edited by rlees85 (2016-05-29 08:44:55)

ooo · 2016-04-11 10:51:00

I can confirm gnome-terminal is failing to start for me under gnome-shell with this error:

$ gnome-terminal 
Error creating terminal: Message recipient disconnected from message bus without replying

Also:

$ ssh-add -l
Could not open a connection to your authentication agent.

I'm not using any login manager, but start gnome-session with startx.
Thanks for investigating this.

rlees85 · 2016-04-11 14:00:01

I assume your keyring is unlocked before trying ssh-add ? Either way I guess I need to raise a bug... (somehow)

wba072 · 2016-04-11 17:19:51

I'm using GNOME 3.20 with GDM.

echo $SSH_AUTH_SOCK
/run/user/1000/keyring/ssh

ssh keyring works fine for me (ssh-add -l works fine). gnome-terminal works fine in X, but when I autologin to Wayland it fails to launch (there's an issue with dbus).

Are you using X or Wayland?

rlees85 · 2016-04-11 19:14:22

I am using Cinnamon which at the moment only supports X. But yeah I don't know where to look, hopefully more people will reply to help build up an idea (or even better a package update over the next few days fixes it automagically)

edit: tried setting it manually in /etc/profile and writing the steps to a log file. It sets the variable fine but when trying to use the variable once the DE is fully loaded it is blank again. So it seems it is probably getting set, but then cleared again.

Last edited by rlees85 (2016-04-11 20:59:00)

rlees85 · 2016-04-12 08:40:53

Rolling back to 3.18 for gnome-keyring and seahorse fixes this. Its a shame that Remmina is also broken.... (blank screen when trying to SSH, does nothing)

chocolateboy · 2016-04-15 14:21:42

rlees85 wrote:

- Cinnamon
- Lightdm
- Gnome-Terminal
- Gnome-Keyring

Same setup here.

Can anyone else with gnome-keyring installed do the following:
ssh-add -l
If it says:
Could not open a connection to your authentication agent.
You have the same problem.

Yes, same result for me. There was a similar issue with Gnome 3.16, and the workaround posted here seems to be working for me:

echo "export SSH_AUTH_SOCK=/run/user/1000/keyring/ssh" >> ~/.profile
exec $SHELL -l

rlees85 · 2016-04-15 15:20:13

Cheers for the tip... It'll do until its fixed properly I just want to make the developers aware as it seems not many people use it.

Arch Linux

#1 2016-04-11 10:35:06

[SOLVED] Another GTK3.20 Problem: SSH_AUTH_SOCK not set

#2 2016-04-11 10:51:00

Re: [SOLVED] Another GTK3.20 Problem: SSH_AUTH_SOCK not set

#3 2016-04-11 14:00:01

Re: [SOLVED] Another GTK3.20 Problem: SSH_AUTH_SOCK not set

#4 2016-04-11 17:19:51

Re: [SOLVED] Another GTK3.20 Problem: SSH_AUTH_SOCK not set

#5 2016-04-11 19:14:22

Re: [SOLVED] Another GTK3.20 Problem: SSH_AUTH_SOCK not set

#6 2016-04-12 08:40:53

Re: [SOLVED] Another GTK3.20 Problem: SSH_AUTH_SOCK not set

#7 2016-04-15 14:21:42

Re: [SOLVED] Another GTK3.20 Problem: SSH_AUTH_SOCK not set

#8 2016-04-15 15:20:13

Re: [SOLVED] Another GTK3.20 Problem: SSH_AUTH_SOCK not set

Board footer