Despite Goldwarden Sending Key, Bitwarden Extension Fails to Receive Key on Librewolf 134.0-1

[InputandOutput]

Hello all,

After installing the AUR package for goldwarden (version 0.3.6) on an arch linux system and went through the setup as described in the provided wiki ("Getting Started" and "Browser Biometric Approval" for firefox/librewolf, setting up browser biometrics on the bitwarden extension was simple as enabling the feature on the Bitwarden firefox extension. However, when testing for the unlock function by inputting the goldwarden pin, the logs from journalctl did show that goldwarden had sent the key:

Jan 22 13:42:34 workman goldwarden[46408]: [INF] [13:42] [Goldwarden > Pinentry] >>> Got approval from user Jan 22 13:42:34 workman goldwarden[46408]: [INF] [13:42] [Goldwarden > Actions] >>> Browser Biometrics: Approved, getting key... Jan 22 13:42:34 workman goldwarden[46408]: [INF] [13:42] [Goldwarden > Actions] >>> Browser Biometrics: Sending key...

However, using the developer tools for the Bitwarden Password Manager showed that the extension had not received the key it expected, and was not able to unlock with biometrics. The "Unable to set key: Error: No key received" error is shown below:

Unable to set key: Error: No key received [console-log.service.ts:51:16](webpack:///libs/common/src/platform/services/console-log.service.ts) write console-log.service.ts:51 error console-log.service.ts:28 onMessage nativeMessaging.background.ts:337 o background.js:1 (Async: promise callback) l background.js:1 o background.js:1 (Async: promise callback) l background.js:1 o background.js:1 (Async: promise callback) l background.js:1 ex background.js:1 ex background.js:1 onMessage background.js:1 connect nativeMessaging.background.ts:187 ex background.js:1 ex background.js:1 connect nativeMessaging.background.ts:118

I am unsure if the issue should be due to the project, my setup, or some other cause that I do not know of. Please let me know if clarification is needed for my problem.

[InputandOutput]

(I should also add that I'm using a KDE desktop environment).