We can add this to browser-support: # for U2F yubikey /run/udev/data/c238:[0-9]* r, /run/udev/data/c239:[0-9]* r, /run/udev/data/c240:[0-9]* r, /run/udev/data/c240:[0-9]* r, /run/udev/data/c240:[0-9]* r,
Can someone experiencing this issue adjust /var/lib/snapd/apparmor/profiles/snap.chromium.chromium to have the above, and then run: sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/snap.chromium.chromium and report back if the issue is resolved? If not, please paste any other apparmor denials. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1738164 Title: [snap] U2F doesn't work with yubikey Status in chromium-browser package in Ubuntu: Confirmed Bug description: (initially reported by Daniel at https://forum.snapcraft.io/t/call- for-testing-chromium-62-0-3202-62/2569/50) « U2F (Universal 2nd Factor) isn’t working when signing into my gmail account trying to use my yubikey. This is a USB device which IIRC chromium needs bidirectional communication with. » This requires investigation, but the yubikey I have is too old and doesn't support U2F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
