I had initially commented on this in the comments for issue #693 (YubiKey doesn't works on Snap version). I probably should have opened a new issue instead at that time. I was hoping the issues were related and similar enough that I could just wait for 2.2.1 ... The observed behaviour in the 2.2.1 appimage is identical to that documented in #693 for the 2.2.0 Snap version.

Expected Behaviour

When unlocking a database or changing/creating a master key, the Yubikey should show up in the list of devices in the "Challenge-response" section.

Current Behavior

The Yubikey is not visible in the list of devices (the device list is empty). No amount of plugging/unplugging/ or pressing the "refresh" button will change this. The Yubikey has been configured with a valid challenge response credential in slot #2.

Steps to Reproduce (for bugs)

1. Start KeepassXC
2. Plug in Yubikey (steps 1 and 2 are interchangeable)
3. Create new DB, or open existing DB
4. Yubikey is not available for challenge response authentication

Context

Challenge-response authentication is a major enhancement to KeepassXC, but at the moment seems to be unavailable to Appimage users.

Debug Info

KeePassXC - Version 2.2.1
Libraries:

• Qt 5.9.0
• libgcrypt 1.6.1

Operating system: Linux Mint 18.2
CPU architecture: x86_64
Kernel: linux 4.10.0-35-generic

Enabled extensions:

• KeePassHTTP
• Auto-Type
• YubiKey