Several services (including Google and GitHub) are starting to allow U2F authentication with devices like Yubikeys. The login process is usually something like: 1. Enter username and password 2. Click Next 3. See prompt to touch the button on your U2F device (or chose from a list of different authentication methods like SMS, Authenticator app, etc...) 4. Touch button 5. You are now signed in Chromium crashes on step 3 when the U2F dialog is presented. [aaron@ripley ~]$ chrome (chrome:63961): IBUS-WARNING **: Unable to load /var/db/dbus/machine-id: Failed to open file '/var/db/dbus/machine-id': No such file or directory (chrome:63961): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported [64062:478240768:0506/103526.074133:ERROR:KeyboardEventManager.cpp(427)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState() Received signal 11 SEGV_MAPERR 000000000000 #0 0x0000046b133b <unknown> #1 0x0000046b12f3 <unknown> #2 0x000807c73994 <unknown> [end of stack trace] Calling _exit(1). Core file will not be generated. [aaron@ripley ~]$ I have tested this against the system package and I compiled the ports version. Both suffer from the same problem. It makes it difficult to surf the web when a site can randomly ask to query a U2F token and the brower disappears. :)
An easy way to reproduce the issue without signing up for a GitHub or Google account is go to here: https://demo.yubico.com/u2f Click on the 'Register' tab and put in a username/password like 'test' and 'test', then click 'next'. It will attempt to communicate with the USB device and crash.
*** This bug has been marked as a duplicate of bug 196754 ***