Hi,
My bitwarden keeps logging out on google chrome eventhough i have my system prefrences on log out after system lock. I tried the steps from link down below from someone who had the same issue, but it still doesnt work. Could anyone be of help? Thanks you in advance!
@Mike2189739212 Hi!
What is your OS and version?
What is your Chrome version?
What is your Bitwarden Chrome extension version?
@Nail1684 hi!
Thank you for the quick response, hereby:
I run Chrome and am not having this problem. There is a setting for how long Bitwarden will reamain unlocked. I changed mine ot something like four hours - it was logging out regularly - like 15 minutes I think, which was annoying.
Are you closing and restarting your browser, by any chance? With your Vault Timeout settings, the browser extension is expected to log out anytime that the browser is restarted.
Thank you for the reply. My Vault timeout setting is set on log-out on system lock. I tried changing it to 4 hours, but it doesnt make a difference…
Thank you for the reply. I am closing the browser indeed and that’s what i’m trying to redeem since it is kind of the way I work. I see two options to do so: (1) log out after system lock or (2) log out when restarting the browser. I use the first, which doesnt work, but also the latter doesn’t provide me the hoped solution.
Open a second browser window, minimize it and never use it. This will keep the browser itself running, allowing the vault to remain in memory.
It was my only idea, sorry. I’ve had very good luck with the product. I was locked out for a bit, even with the correct master password, but I think that was an update issue on one end or the other. I really found the short timeout to be annoying. It took me three or four months to get bothered enough to see if there was a choice. I am convinced that there are updates/versions of products that generate conflicts we just can’t sort out, and they eventually solve themselves. Hope you find a solution.
I’m not sure if you are already fully aware of that, but:
I would suggest that you change your Vault Timeout Action from “Log out” to “Lock”. This will give you the option to unlock with a shorter password (a “PIN”) rather than inputting your master password.
Ah, I see… unfortunately, since it is a bit anoying at times. I’m going to use a pin as a first step
Thank you, I have installed the pin! 
It seems from the gitHub issues that there is a fundamental problem with BW recognizing when the system is locked; the API that BW uses seems to not work intuitively and there is no apparent workaround for BW. If this is true, then it needs to be explained better in these forums, instead of sowing seeds of hope that it will be fixed.
@srseibs Welcome to the forum, and thanks for posting the GitHub link.
However, I don’t know what you’re trying to say with the last sentence in your comment. As far as I can tell, nobody in this thread has “sown hope” that the Chrome extension will be able to distinguish between a system lock and a screensaver activation (nor does this mode of failure appear to be relevant to the issue experienced by the OP).
i have my system preferences on log out after system lock.
He said his vault timeout is set to timeout “After System Lock”. According to the issue I stumbled across, this is a known issue with BW that has no workaround or fix.
(Should the “System Lock” option be removed since it seems like a placebo?)
True, but that is coincidental. Ultimately, OP’s issue was that they were closing their browser (which always times out the browser extension, unless the timeout is set to “Never”), and exacerbated by the choice of “Logout” (as opposed to “Lock”) for their timeout action.
If you are having issues with (or just want to draw attention to) the extension timing out when your screen saver is activated, I would suggest starting a new topic.
