Fido2 error - Debian 13, chrome based browsers

[struestyle]

Steps To Reproduce

1. Go to 'github.com'
2. Click on 'sign in'
3. Click on 'Continue with Passkey'

Expected Result

Use bitwarden extension to send fido2 secret to the website

Actual Result

an error message in front : Authentication failed.
error message in the console :
Uncaught (in promise) Error: The operation either timed out or was not allowed. at Messenger.<anonymous> (fido2-page-script.js:304:35) at Generator.next (<anonymous>) at fulfilled (fido2-page-script.js:239:58) (anonymous) @ fido2-page-script.js:304 fulfilled @ fido2-page-script.js:239 Promise.then step @ fido2-page-script.js:241 (anonymous) @ fido2-page-script.js:242 __awaiter @ fido2-page-script.js:238 request @ fido2-page-script.js:288 (anonymous) @ fido2-page-script.js:537 (anonymous) @ fido2-page-script.js:382 fido2_page_script_awaiter @ fido2-page-script.js:378 getWebAuthnCredential @ fido2-page-script.js:494 prompt @ webauthn-get-element.ts:182

Screenshots or Videos

2025-10-10-19-01-07.mp4

Additional Context

bitwarden extension version : 2025.9.0

Operating System

Linux

Operating System Version

Debian 13

Web Browser

Brave

Browser Version

Chromium: 141.0.7390.70 / Brave 1.83.112

Environment Versions

Version: 2025.9.0

SDK: 'main (ab3c7db)'

Version du serveur: 2025.9.2

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-26796
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-26796