Since the problem still exists and I need to use the device, I've done some further debugging.
It seems to be related to the apparmor profile for chrome coming with package apparmor-profiles. After aa-disable usr.bin.chromium-browser things work as normal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796746 Title: Chromium-Browser not recognizing yubikey u2f anymore? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1796746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
