Created attachment 158961 [details] lsusb screenshot. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** KDE Neon provides Firefox with own APT repository, with pre-installed state. However, preinstalled Firefox does not support USB security keys like YubiKey 5. STEPS TO REPRODUCE 1. Run pre-installed Firefox 2. Go to https://webauthnsample.azurewebsites.net/ 3. Click Register or Authenticate button below. OR if you are worrying about security issues: Try GitHub login process with security key enabled account. OBSERVED RESULT You can see a pop-up near by the address bar, but it quickly disappeared. EXPECTED RESULT A pop-up that asks you to insert security key or enter PIN code to continue appeared under the address bar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27(Based on Ubuntu 22.04 LTS), KDE Plasma 5.27.5 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 5.19.0-41-generic (64Bit) Graphic Platform: X11, Wayland (Both platform shows same error) ADDITIONAL INFORMATION - Firefox installed with Flatpak(from flathub) works well with security keys, but frequently crashed without crash report and not working with KIME (one of linux Korean IME) - Firefox installed with snap works well with security keys, but it does not support preinstalled CJK fonts. - Chromium installed with Flatpak works well with security keys. - Firefox Nightly(firefox-trunk package) installed by APT PPA(https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/ppa) does not work with security keys. - YubiKey Manager (CLI, installed with APT PPA by Yubico) detects YubiKey inserted. - lsusb shows YubiKey inserted in this laptop. - Firefox Nightly installed on Kubuntu 22.04, installed with snap works very well. However, it was tested three months ago.
This bug is a duplicate of #468681 *** This bug has been marked as a duplicate of bug 468681 ***