** Changed in: snapd
Status: Fix Committed => Fix Released
** No longer affects: chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940467
Title:
[snap] Nitrokey FIDO2
** Changed in: snapd
Status: Confirmed => Fix Committed
** Changed in: snapd
Milestone: None => 2.53
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940467
Title:
[snap] Nitrokey FIDO2
Related pull request here: https://github.com/snapcore/snapd/pull/10642
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940467
Title:
[snap] Nitrokey FIDO2 does not work with Chromium snap
To
This is because snapd's u2f-devices interface lacks this rule. See my
response here: https://forum.snapcraft.io/t/nitrokey-fido2-does-not-
work-with-chromium-snap/26098/2
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
**
** Description changed:
I have a Nitrokey FIDO2, which works fine with the Firefox deb package.
However, it does not work at all with the Chromium snap. I have
libu2f-udev installed.
- This problem can be fixed by adding the following line to
+ This problem can be fixed by adding the
