The bug described here looks like the one I'm experiencing. I have multiple yubikeys which I use for SSH and GPG (occasionally U2F but that doesn't appear to be affected by this). If I just enable the pcscd service, the daemon doesn't auto-start after a reboot. Running ssh or gpg commands fails to access the key. I also need to enable the socket. Then the daemon auto-starts and I can use ssh/gpg:
$ systemctl enable pcscd
# after a reboot, pcscd is stopped, ssh/gpg unable to access the key. Need to start pcscd manually.
$ systemctl enable pcscd.socket
# now after reboot both the socket and the service are running and ssh/gpg works
It wasn't like this with 20.04, there enabling pcscd.service was enough.
Hope this helps others with the issue, and/or the maintainers to address it.
The bug described here looks like the one I'm experiencing. I have multiple yubikeys which I use for SSH and GPG (occasionally U2F but that doesn't appear to be affected by this). If I just enable the pcscd service, the daemon doesn't auto-start after a reboot. Running ssh or gpg commands fails to access the key. I also need to enable the socket. Then the daemon auto-starts and I can use ssh/gpg:
$ systemctl enable pcscd
# after a reboot, pcscd is stopped, ssh/gpg unable to access the key. Need to start pcscd manually.
$ systemctl enable pcscd.socket
# now after reboot both the socket and the service are running and ssh/gpg works
It wasn't like this with 20.04, there enabling pcscd.service was enough.
Hope this helps others with the issue, and/or the maintainers to address it.