You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open Bitwarden in any workspace (we'll say workspace 1).
Set a vault timeout (Edit > Settings > Security > Vault Timeout). Mine is set for 2 minutes.
Open a browser on workspace 2 and go to a website that requires username and password saved in your vault.
Copy and paste login credentials from Bitwarden, and begin doing whatever you need to do on said website.
Expected Result
Bitwarden locks my vault after 2 minutes.
Actual Result
Bitwarden does lock my vault after 2 minutes. However, when it locks, it automatically forces my screen back to workspace 1.
Screenshots or Videos
No response
Additional Context
I'm unsure if this is actually a Bitwarden problem. This behavior is new, but that doesn't necessarily mean that it's from an update to Bitwarden. My first thought was that it's either a Bitwarden problem or a problem with my window manager (kwin). From what I've been able to determine so far, it doesn't seem to be a kwin problem, but I'm still investigating. Perhaps this is neither a Bitwarden nor a kwin problem, but at this time I believe Bitwarden to be the most likely culprit. I don't know if it would be from upstream Bitwarden or if it has something to do with how the Arch Linux devs packaged the binary in their repos. I'll be looking into this as well.
Operating System
Linux
Operating System Version
Arch Linux using Linux 6.10.9-arch1-2 kernel.
Installation method
Other
Build Version
Version 2024.8.1 Shell 31.6.0 Renderer 126.0.6478.234 Node 20.17.0 Architecture x64
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.
The text was updated successfully, but these errors were encountered:
Commenting to add info. I'm on a laptop, not a desktop with multiple displays with workspaces assigned to certain displays, nor do I have a rule set for Bitwarden to live in a specific workspace. I have no such rules set in my window manager. All of my applications open in whichever workspace I open them in, and they stay there unless I move them. So Bitwarden is not stealing workspaces from other applications. It's simply forcing a workspace change back to its own workspace when my vault locks.
Since I only have the one display, being automatically forced back to Bitwarden's workspace is extremely disruptive. For example, it keeps interrupting me while I'm trying to fill out forms in my web browser. I've considered just manually locking Bitwarden every time, but I don't always want to lock it right away. Sometimes I need to come back multiple times when I need to enter a password for authentication more than once.
Just to confirm, is this on KDE? Wayland or X?
Further, do you happen to have the browser integration enabled?
And finally, is this the AUR version, or a sandboxed version like flatpak?
Just to confirm, is this on KDE? Wayland or X? Further, do you happen to have the browser integration enabled? And finally, is this the AUR version, or a sandboxed version like flatpak?
My apologies. This is on KDE Plasma in a Wayland session. I do not have browser integration enabled. I leave it disabled intentionally. I'm using the version packaged in the Arch Linux Extra repo. This github repo is its upstream.
Steps To Reproduce
Expected Result
Bitwarden locks my vault after 2 minutes.
Actual Result
Bitwarden does lock my vault after 2 minutes. However, when it locks, it automatically forces my screen back to workspace 1.
Screenshots or Videos
No response
Additional Context
I'm unsure if this is actually a Bitwarden problem. This behavior is new, but that doesn't necessarily mean that it's from an update to Bitwarden. My first thought was that it's either a Bitwarden problem or a problem with my window manager (kwin). From what I've been able to determine so far, it doesn't seem to be a kwin problem, but I'm still investigating. Perhaps this is neither a Bitwarden nor a kwin problem, but at this time I believe Bitwarden to be the most likely culprit. I don't know if it would be from upstream Bitwarden or if it has something to do with how the Arch Linux devs packaged the binary in their repos. I'll be looking into this as well.
Operating System
Linux
Operating System Version
Arch Linux using Linux 6.10.9-arch1-2 kernel.
Installation method
Other
Build Version
Version 2024.8.1 Shell 31.6.0 Renderer 126.0.6478.234 Node 20.17.0 Architecture x64
Issue Tracking Info
The text was updated successfully, but these errors were encountered: