Bug report: 1PW not locking as expected
Just noticed yesterday: 1Password is not (auto-)locking in the way that it always has before; i.e., after the computer itself has locked due to inactivity.
This is the case even when I've closed the 1PW app, and then the computer has gone to sleep and locked the screen. Most recent example: walked away from computer last night around 7pm, started using computer again this morning around 5am (had to log into Windows). Just now, fired up 1PW, and was not prompted for the master password.
I am only using the desktop app. I do not have the browser extension installed.
Just verified that I can lock the app manually.
[ETA] In Settings > Security:
• Auto-lock: Lock after the system is idle for: 10 minutes
• Auto-lock: Lock 1Password when computer locks (checked)
• Clipboard: Remove copied information and one-time passwords after 90 seconds (checked)
No other boxes are checked.
1Password Version: 8.10.33
Extension Version: n/a
OS Version: Windows 10
Browser: n/a
Comments
-
Hi @bjkeefe! It's definitely strange that 1Password 8 isn't following your auto-lock settings even after your device has been idle for long enough to sleep.
Could you email in to
support+forum@1password.comwith a diagnostics report from 1Password, so we can look into this further?With your email please include:
- A link to this thread: https://1password.community/discussion/146170/bug-report-1pw-not-locking-as-expected#latest
- Your forum username:
bjkeefe
Once you get a response with a Support ID, please post that number here so we can connect the dots. Thanks!
0 -
Thanks for the reply. I have sent the email. Will post Support ID when I get a response to that email.
Update: got it. Here is the relevant line:
Your support ticket ID is CDG-58666-157.
0 -
Update (for anyone who happens across this thread):
While I don't know what caused the non-locking problem, it appears to have cleared itself; i.e., after about a week, the problem has not reappeared.
It could well be that all it took was rebooting the computer. The support team speculated that perhaps there was some background process that was running that 1PW interpreted as "computer still active," despite the computer appearing to be in sleep mode. If so, perhaps the rebooting killed that process, and it isn't one that restarts automatically upon system restart.
0
