https://blog.apdu.fr/posts/2024/04/gnupg-and-pcsc-conflicts-episode-2/
I do not use GnuPG with a smartcard. So I don't know which configuration
is more stable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in
I don't recommend running with pcscd, it's much more stable to run with
direct access, but I do not know why it doesn't seem to work for you, it
certainly does for me.
It failing with pcscd is nice, it not telling us why and how to fix it
is bad UX though.
** Changed in: gnupg2 (Ubuntu)
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
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
** Changed in: archlinux-lp
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/2061708
Title:
Yubikey stopped working after noble
According to the upstream bug, this appears to be a new intended
behavior with newer gnupg2:
https://dev.gnupg.org/T6871
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
I managed to get it working as a user by manually starting pcscd.service
and with the following to force scdaemon to use it.
# cat ~/.gnupg/scdaemon.conf
card-timeout 5
disable-ccid
To me this seems to be a regression in behavior from 2.2.27-3ubuntu2.1
to 2.4.4-2ubuntu17.
** Bug watch added:
6 matches
Mail list logo
