Errors when syncing, needs secret service access

[LinAGKar]

Recently, BitWarden was changed to use secure storage: bitwarden/clients#8651 (comment), and they have instructions there for how to give BitWarden snap access to Secret Service. This Flatpak seems to experience similar issues as what is mentioned there, and probably also needs permissions added to let it access Secret Service.

[samhanna84]

I'm having the same issue

[ghisvail]

Secrets service is already enabled.

Looks like the issue is being worked on upstream.

[LinAGKar]

Looks like the issue is being worked on bitwarden/clients#8776.

That issue from what I can tell is about adding a fallback for when secret storage is not available. If that affects the flatpak, that presumably means secret storage is not working in the flatpak.

[lucasmz-dev]

I had this issue for a second when I tried Mint for a while, then went back to Fedora and I could see entries for Bitwarden in GNOME's Passwords and Keys, so it seems like it's being used. Now again in Mint 22, no issue like before at least.

[ghisvail]

@lucasmz-dev I am confused about your comment. Do you confirm the issue or not?

[lucasmz-dev]

I was, now it's fine /shrug

[quexten]

This sounds more like an issue with the desktop environment not including a functioning secret service to be honest. For the polkit biometrics work, the secret service is required with no fallback (otherwise the feature is disabled), and it worked fine during my testing on gnome in flatpak, meaning the flatpak config is fine.

For tokens for a while, secret storage was required (also when this issue was reported), but this was fixed by bitwarden/clients#8913 which adds a fallback to "insecure" file based storage. So syncing errors should not happen anymore, even without a functioning secret service.

[LinAGKar]

I do have Secret Service available