The terminal app hasn't been updated recently, so it's reasonable to think that there's something different in OTA-10.
Having a look at the commit log[1] for the latest release, I see that "gnome-keyring" package has been added to the system image.
A quick search[2] on Google suggests that this may cause the problem you mention.
The blog post at [2] suggests to workaround the problem by running:
$ SSH_AUTH_SOCK=0 ssh <username>@<hostname>
Therefore I'm adding "canonical-devices-system-image" project as affected, and marking the report as Incomplete for terminal-app (so I get notified of any change/update of the report).
Hi,
The terminal app hasn't been updated recently, so it's reasonable to think that there's something different in OTA-10.
Having a look at the commit log[1] for the latest release, I see that "gnome-keyring" package has been added to the system image.
A quick search[2] on Google suggests that this may cause the problem you mention.
The blog post at [2] suggests to workaround the problem by running:
$ SSH_AUTH_SOCK=0 ssh <username> @<hostname>
Therefore I'm adding "canonical- devices- system- image" project as affected, and marking the report as Incomplete for terminal-app (so I get notified of any change/update of the report).
=====
[1] http:// people. canonical. com/~lzemczak/ landing- team/ota/ ota-10. commitlog /chrisjean. com/ubuntu- ssh-fix- for-agent- admitted- failure- to-sign- using-the- key/
[2] https:/