1

I have OS X set to require my password immediately after “sleep or screen saver begins” (and I'm assuming this includes display sleep). Since Mavericks, there seems to be a one-second grace period: if I trigger the screen saver or put the display to sleep, and then immediately hit the shift key or move the mouse, I'm dropped back into my account with no password prompt.

I'm currently running Yosemite.0 (10.10.0). Is this a bug in Mavericks that never got fixed, or what? More importantly, how do I get it to require my password immediately?

2

By design the first action system does is to save your work in a large file (depending what you had going on) so to be able to wake up exactly to where you left of. Once that is done the next step is to lock it with password.

That action does require time (writing the image), so if you are very quick you can catch your system in the writing action.

Here is a example:

Close lid-->

11/15/14 07:54:30.000 WindowServer[86]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fdfc2449050(2001)

11/15/14 07:54:30.038 WindowServer[86]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x7fdfc2449050(2001)

Open lid-->

11/15/14 07:54:33.928 WindowServer[86]: CGXDisplayDidWakeNotification [174799469151647]: posting kCGSDisplayDidWake
11/15/14 07:54:33.929 WindowServer[86]: handle_will_sleep_auth_and_shield_windows: Deferring.
  • Why does this prevent the system from immediately prompting for a password, though? If I catch it while it's writing this file out, shouldn't it just stop writing the file (or finish—doesn't matter, really) in the background and…throw up a password prompt? I guess I just don't see how this is relevant! – Blacklight Shining Nov 15 '14 at 16:28
  • If you look at my console log, it first writes the recovery situation, then it locks, it can not lock before the info is saved. In my case it took .038 Milly seconds to do that. – Ruskes Nov 15 '14 at 16:40
  • 1
    What you are asking is not possible. The password is for the saved wake-up screen, so it has to be saved first before a password is assigned to it. – Ruskes Nov 15 '14 at 16:48
  • I see nothing in your log that explicitly says writing file or locking, only things that look like function|method names and memory addresses. I still don't understand why it can't simply require a password immediately after the user asks for the system to be locked. It seems trivial to me to set a flag that means we're locked now; require a password to unlock, and then do the file writing afterward. – Blacklight Shining Nov 15 '14 at 19:47
  • "device_generate_desktop_screenshot" OK, could you provide your console output for us to compare please. – Ruskes Nov 15 '14 at 20:12

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .