I have seen this issue across three different Ubuntu releases now,
latest being 22.04. After each upgrade, SSH logins (and git repo access)
using my GPG hardware token stop working. The workaround specified in
the descriptions works. I have been doing that after each Ubuntu
upgrade.
The lack of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnupg2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901724
Title:
Apparently the birthplace of that script is found here:
GPG_AGENT_INFO and SSH_AUTH_SOCK not set in wayland sessions
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855868
** Bug watch added: Debian Bug tracker #855868
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855868
--
You
> I thought gnome-shell started its own agent for ssh on startup?
My keys are on hardware security devices and I also use gpg-agent-forwarding,
so afaik gnome-keyring-ssh will not do in this setup.
> Or did you configure your system to run the gnupg agent before starting gnome?
The way I
I thought gnome-shell started its own agent for ssh on startup? Or did
you configure your system to run the gnupg agent before starting gnome?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
