Hello,
I have two systems running Arch Linux with KDE Plasma–both are fully updated and have this udev rule. On one of my systems, the U2F key doesn’t work. It lights up when I plug it in, but it doesn’t work with any U2F service in either chrome or firefox. Here are the only relevant journalctl entries I could find, which occur after plugging the device in:
r 03 17:57:31 arch kernel: usb 1-1.2: new full-speed USB device number 3 using ehci-pci
Mar 03 17:57:31 arch kernel: usb 1-1.2: New USB device found, idVendor=20a0, idProduct=4287, bcdDevice= 1.00
Mar 03 17:57:31 arch kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 03 17:57:31 arch kernel: usb 1-1.2: Product: Nitrokey FIDO U2F
Mar 03 17:57:31 arch kernel: usb 1-1.2: Manufacturer: Nitrokey
Mar 03 17:57:31 arch kernel: usb 1-1.2: SerialNumber: 0000000000000000
Mar 03 17:57:31 arch kernel: hid-generic 0003:20A0:4287.0006: hiddev0,hidraw5: USB HID v1.11 Device [Nitrokey Nitrokey FIDO U2F] on usb-0000:00:1a.0-1.2/input0
Mar 03 17:57:31 arch mtp-probe[4014]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
Mar 03 17:57:31 arch mtp-probe[4014]: bus: 1, device: 3 was not an MTP device
Mar 03 17:57:31 arch plasmashell[1421]: UdevQt: unhandled device action "bind"
Mar 03 17:57:31 arch org_kde_powerdevil[1482]: UdevQt: unhandled device action "bind"
Mar 03 17:57:31 arch mtp-probe[4030]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
Mar 03 17:57:31 arch mtp-probe[4030]: bus: 1, device: 3 was not an MTP device
Mar 03 17:57:31 arch org_kde_powerdevil[1482]: UdevQt: unhandled device action "bind"
Mar 03 17:57:31 arch plasmashell[1421]: UdevQt: unhandled device action "bind"
Note that the journalctl entries look pretty much identical on the system where the FIDO u2f key works. The only real difference I can think of between the two machines is the one that works is running the LTS Kernel, while the machine that doesn’t work is running the latest 4.20 Kernel.
Do you have any idea how I could begin troubleshooting? Is there another log I should look at for issues like this besides the syslog?
Thanks!