I can confirm we get the same issues on Ubuntu Destktop 18.04.4 + Mate
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1586835
Title:
ssh-agent fighting gnome-keyring on Ubunt
I have a very similar experience on Ubuntu MATE 18.04.
/run/user/1000/keyring/ssh is opened by gnome-keyring-daemon
/run/user/1000/keyring/.ssh is opened by /usr/bin/ssh-agent
$SSH_AUTH_SOCK points to /run/user/1000/keyring/ssh
When I try to open an SSH session to another machine it hangs just af
I am also experiencing this problem on Ubuntu 17.04. I have seen
suggestions in Internet forums that Gnome Keyring does not properly
support all SSH key formats. I was using a 4096 bit RSA key in the
situation that failed. When I changed to a 2048 bit RSA key the problem
disappeared.
--
You recei
** Changed in: gnome-keyring (Ubuntu)
Assignee: HECTOR DAVID (hektve) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1586835
Title:
ssh-agent fighting g
** Changed in: gnome-keyring (Ubuntu)
Assignee: (unassigned) => HECTOR DAVID (hektve)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1586835
Title:
ssh-agent fighting g
Are you all using the GNOME3 Staging PPA? If so, this is a known issue
that I don't think will be fixed there.
I believe this bug was fixed in Ubuntu GNOME 16.10 so I suggest
upgrading. If you do, you will need to upgrade twice per year until
18.04 LTS.
--
You received this bug notification beca
Hi, thanks for the info in this thread. It lead me into a work-around
that seems to work for me.
The scenario in my case: something is defining SSH_AUTH_SOCK but there's
no ssh-agent running, despite use-ssh-agent being set in
/etc/X11/Xsession.options. gnome-keyring-deamon is however running,
whe
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1586835
When reporting bugs in the future please use apport by using 'ubuntu-
b
Here is the workaround:
1. disable start of ssh-agent from openssh by commenting out the use-ssh-agent
line from file "/etc/X11/Xsession.options".
2. start ssh-agent from gnome-keyring daemon and set SSH_AUTH_SOCKET variable
by adding the following to ${HOME}/.profile:
# From man gnome-keyring-da
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpa
I have located a way to disable ssh-agent by commenting out the use-ssh-
agent line from file "/etc/X11/Xsession.options". But even after doing
this it is not guaranteed that the $SSH_AUTH_SOCK variable will be set
when I open a new terminal, even while doing so several minutes after I
have logged
11 matches
Mail list logo
