Lock after computer is idle for... does not work
Comments
-
Greetings @stanh,
When you say 1Password doesn't lock after 60 minutes are you counting idle time as 60 minutes since you last used 1Password (but have been using the Mac) or 60 minutes since you touched the keyboard or mouse? When we say computer is idle we're talking about a counter that OS X keeps and it's based on user activity. Interacting with the computer at all resets the counter so that would be 60 minutes without touching the keyboard or mouse. Could that explain what you're seeing at all or are you saying 1Password doesn't lock after you've walked away from your computer for over an hour?
0 -
1Password doesn't lock after I've walked away from my computer for over an hour.
0 -
Greetings @stanh,
Can I ask what other Auto-lock settings you have enabled and in System Preferences > Energy Saver what do you have your Mac set to do. I'm wondering if your Mac is going to sleep and this is somehow messing up the idle timer. I don't know the answer to this, it's just a thought I had and something that might be worth exploring.
0 -
Here's a screen shot of my energy saver preferences. Let me know if there's something amiss here.
0 -
Hi @stanh,
Thanks for that screenshot, it helps narrow this down.
The next step is to see if there is another process running on the machine that is preventing the system from thinking its idle.
Can I get you to:
Open /Applications/Utilities/Terminal.app
Copy & Pastepmset -g assertions
Press the return key to run the command
Copy the text and paste it hereRudy
0 -
Okay--here it is:
Stans-iMac:~ stanhoffman$ pmset -g assertions
2016-04-11 11:21:38 -0700
Assertion status system-wide:
BackgroundTask 0
ApplePushServiceTask 0
UserIsActive 1
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
ExternalMedia 1
PreventUserIdleSystemSleep 0
NetworkClientActive 0
Listed by owning process:
pid 55(powerd): [0x000000430008012c] 140:08:30 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"
pid 101(hidd): [0x0007b30300090968] 00:00:18 UserIsActive named: "com.apple.iohideventsystem.queue.tickle"
Timeout will fire in 1181 secs Action=TimeoutActionRelease
Kernel Assertions: 0x10c=USB,BT-HID,MAGICWAKE
id=501 level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.14200000 owner=USB2.0 Hub
id=502 level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.14100000 owner=MacBook Air SuperDrive
id=503 level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.14a00000 owner=Minimus USB 3
id=504 level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.14220000 owner=Keyboard Hub
id=505 level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.14240000 owner=USB2.0 Hub
id=506 level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.14242000 owner=d2 quadra (button)
id=507 level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.14244000 owner=HL-5340D series
id=508 level=255 0x100=MAGICWAKE mod=12/31/69, 4:00 PM description=en1 owner=en1
id=509 level=255 0x8=BT-HID mod=12/31/69, 4:00 PM description=com.apple.driver.IOBluetoothHIDDriver owner=BNBMouseDevice
id=510 level=255 0x8=BT-HID mod=12/31/69, 4:00 PM description=com.apple.driver.IOBluetoothHIDDriver owner=BNBTrackpadDevice
Idle sleep preventers: IODisplayWrangler0 -
Hi @stanh,
It looks like we've got a bug here that's going to need further investigation on our end in order to resolve.
In 10.11, if you have your display set to go to sleep its not actually counting that time as part of the idle time. I was able to test this by setting 1Password to lock after 2 minutes, and for the screen to sleep after 1 minute; The screen actually went to sleep at the 2 minute mark, this would normally be the point when 1Password locks, but instead it was unlocked when i woke the machine from its display slumber.
In the mean time, might i suggest setting the auto-lock time period to be something less than your display sleep time.
Rudy
0 -
Okay. Thanks for getting to the bottom of this.
0