Brave browser extension vault lock settings not working (Linux Fedora)

[terry9873]

Steps To Reproduce

Fedora 39 and 40
Brave browser
Bitwarden extension
Set lock settings in extension to 'On system lock'
Then lock system
It doesn't lock

Expected Result

Lock

Actual Result

Unlocked

Screenshots or Videos

No response

Additional Context

I have tried this on various machines on both Fedora 39 and 40. I like my vault to lock when my operating system locks (5 mins of inactivity if i leave my desk)
It never locks. I locked the OS/system manually 24 hours ago, came and unlocked it, BW extension in Brave is not locked.

Operating System

Linux

Operating System Version

Fedora 39/40

Web Browser

Brave

Browser Version

Version 1.65.132 Chromium: 124.0.6367.202 (Official Build) unknown (64-bit)

Build Version

2024.4.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.

[daniellbw]

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

[terry9873]

Thanks. Sorry, no further info. It's still the same. I used exactly the same settings for years on Mac (also on Brave browser), and it worked. if my machine locked due to inactivity, i'd have to unlock the vault when I come back. on Fedora, in 2 different brave profiles, i have those same settings but I haven't had to unlock the vault once since last reboot (and it's been left unattended (and locked) for many hours, many times.
thanks again, fingers crossed someone finds the problem

[quexten]

Hey @terry9873 , since you mention Ubuntu / Fedora, was the desktop environment Gnome? Do you know if you were using X11 or wayland? And finally, do you know if you were using snap/flatpak or an unsandboxed packaging format (deb/rpm/appimage) for the browsers?

[terry9873]

oops, used wrong machine!

Hi, I think I sussed it. I WAS using a sandboxed version of Brave, but switched to RPM following instructions here: https://brave.com/linux/

Yes it's Gnome DE and Wayland.

Since I switched to RPM it's working properly again :)

[quexten]

Thank you for confirming. I guess brave/chrome snap/flatpak do not have the dbus apis passed into the sandbox. Might have to create upstream issues.

[quexten]

flathub/com.brave.Browser#634

[quexten]

flathub/com.google.Chrome#316

[quexten]

flathub/org.chromium.Chromium#416

[rany2]

flathub/io.github.ungoogled_software.ungoogled_chromium#42

[closebot-bw]

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (October 15, 2025) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

• Comment on this issue to show continued interest
• Provide any additional information or updates
• Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

[closebot-bw]

🔒 Issue Closed Due to Inactivity

This issue has been automatically closed due to lack of activity for an extended period. We periodically review and close inactive issues to help maintain our issue tracker and focus on current priorities.

If this issue is still relevant:

• Please create a new issue with updated information
• Include steps to reproduce the problem if it's a bug report
• Mention if this issue still occurs in the latest version

Thank you for your contribution to this project. Your feedback helps us improve! 🙏