Locking the keychain and attempting to unlock will fail. username and server are forgotten.

Steps To Reproduce

Hello. I'm having a weird issue on my FreeBSD machine using Chromium and the Bitwarden browser extension (2022.5.0). After I log into bitwarden, locking the keychain will cause it to automatically forget the username + server that the keychain was associated with. This means that when I try to unlock the keychain, I will be prompted for the passphrase, but typing it in and attempting to submit the request won't do anything since it no longer has the user/server. The firefox + bitwarden (1.58.0 (May 8, 2022)) instance works fine on this same machine.

Install Chromium on FreeBSD 13.1-STABLE (Should be the same behavior on 13.1-RELEASE) via pkg install chromium. Current version as of today: chromium-102.0.5005.61_2.
Open Chromium
Install the Bitwarden Browser Extension via the Chrome Web Store. Currently installed version as of today: 2022.5.0
Log into your bitwarden account.
Close the browser (It should auto lock on default settings)
Open Chromium
Try to login. It won't let you do anything once you press enter since there is no username or server associated to the bitwarden instance. You'll need to fully log out and log back in.

Expected Result

Typing in my passphrase correctly at the bitwarden unlock screen should successfully unlock the toolchain.

Actual Result

Keychain remains locked and typing the passphrase performs no action.

Screenshots or Videos

You can see the following line at the bottom is missing the expected information: Logged in as on

Additional Context

No response

Operating System

Linux

Operating System Version

FreeBSD 13.1-STABLE (There was no FreeBSD option above)

Web Browser

Chrome

Browser Version

Version 102.0.5005.61 (Official Build) (64-bit)

Build Version

2022.5.0

bitwarden / clients