Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screensaver enable password not working #421

Closed
tomcat335 opened this issue Oct 1, 2015 · 31 comments
Closed

Screensaver enable password not working #421

tomcat335 opened this issue Oct 1, 2015 · 31 comments

Comments

@tomcat335
Copy link

The function to enable the screensaver password when arriving at a location doesn't seem to be working. I'm on MacOS 10.11 and it seems to have started after I upgraded.

@dustinrue
Copy link
Owner

dustinrue commented Oct 2, 2015 via email

@tomcat335
Copy link
Author

Running version 1.6.1.

@ColdDevil
Copy link

Same for me with 10.11 and 1.6.1. Also forcing a context does not help.. Although the message is shown that the screensaver password got (de)activated it does not work.

@briemens
Copy link

I can even add that the Require Password checkbox is checked, but OS X 10.11 doesn't pick it up until you manually disable/enable it.

The apple script on this Stack Exchange page is working for me: http://apple.stackexchange.com/questions/51443/disable-screensaver-password-requirement-from-command-line

@gfarrell
Copy link

(1.6.1)

I've found that ControlPlane says it's enabling/disabling the screensaver password, and the box is checked/unchecked as appropriate in system preferences, but that OSX does not take any notice of this, unless I do it manually.

The apple script from SE worked for me too (reposted here for posterity):

sudo osascript -e 'tell application "System Events" to set require password to wake of security preferences to false'

@timothykang
Copy link

I don't have the ability to test it, but I am pretty sure the action no longer works even for <10.11.

I believe this is related to fb44351, in that the deleted line was there to cause the setting to be "reloaded" (see https://web.archive.org/web/20141112135724/http://hintsforums.macworld.com/showthread.php?t=49718#13).

At minimum the deleted line probably needs to be restored and a check for <10.11 be made, but unfortunately that would not fix this action for 10.11.

@repertor
Copy link

Still does not work on 10.11.1

@DHKaplan
Copy link

Just discovered this support site. I'm also on 10.11.1, running CP 1.6.1 and can manually set the password requirement and have it work, but if CP tries, IT thinks it's doing it but it is not activating it.

@p3ppo
Copy link

p3ppo commented Dec 9, 2015

Can confirm this, I have the same problem. I'm on 10.11.1, running ControlPlane 1.6.1. The checkbox is checked/unchecked in System Preferences, but OS X doesn't care, unless you do it manually.

Edit: Now on OS X 10.11.2, same problem.

@JohannesHoffmann
Copy link

I have the same problem... really looking forward for a fix

@kingmatusevich
Copy link

have this problem too, 10.11

@dreammaker
Copy link

@timothykang, 1.6.1 works on OS X 10.10. I was using the enable/disable password until just recently when I upgraded to El Capitan, and it stopped working.

@ghost
Copy link

ghost commented Jan 25, 2016

Same problem as the rest, won't work in El Capitan (10.11.3)

@lhaeger
Copy link

lhaeger commented Feb 7, 2016

I was hoping 1.6.2 solves this, but unfortunately is doesn't...

@ColdDevil
Copy link

Version 1.6.2 changes the checkbox in OS X preferences but it still has no effect unfortunately.

@Pulloverman
Copy link

Same with Version 1.6.2, unfortunately still does not work under 10.11.3.

@richellis
Copy link

Workaround: put the AppleScript referenced by @gfarrell in a shell script and then have ControlPlane fire the script using a System Action.

I didn't include the sudo in the script and it works fine.

#!/bin/sh
osascript -e 'tell application "System Events" to set require password to wake of security preferences to false'

Make a corresponding script with the last value set to true to have a script that re-enables the screensaver password:

#!/bin/sh
osascript -e 'tell application "System Events" to set require password to wake of security preferences to true'

snip20160209_6

@tomcat335
Copy link
Author

Thanks for the tip! Adding the shell scripts worked for me. Nice workaround.

@p3ppo
Copy link

p3ppo commented Feb 10, 2016

Can confirm, same with Version 1.6.2. Still does not work under 10.11.3.
I'm using the shell script workaround. Thanks @gfarrell and @richellis 👍

@ColdDevil
Copy link

Thanks! Great workaround! 😄 👍

@dustinrue
Copy link
Owner

I incorporated the apple script into ControlPlane and it is used for 10.11. I'll be pushing out an update with it soon.

@garee76
Copy link

garee76 commented Mar 8, 2016

Still not working for me! Control Plane 1.6.4 and OSX 10.11.3

@richellis
Copy link

Me neither, I went back to my workaround shell scripts. Those still work great. 

On Tue, Mar 8, 2016 at 1:00 PM -0800, "garee76" notifications@github.com wrote:

Still not working for me! Control Plane 1.6.4 and OSX 10.11.3


Reply to this email directly or view it on GitHub.

@dustinrue
Copy link
Owner

I'm testing this and it's working perfectly on my system.

@tharwan
Copy link

tharwan commented Oct 3, 2016

stopped working for me again with 10.11.6.

@tomcat335
Copy link
Author

Same with me on 10.12, and the script workaround doesn't seem to be working properly either.

@fingolfin
Copy link

Also doesn't work for me on 10.11.6 with Control Plane 1.6.5

@dreammaker
Copy link

The script workaround used to work for me on 10.11, but even the script stopped working for me after upgrading to 10.12 Sierra. I'm using Control Plane 1.6.5.

@dustinrue
Copy link
Owner

I'll be honest and say that I haven't actually looked into this, but if history has taught me anything about this feature, Apple has slowly improved the security of the password lock with each release. It's highly likely this cannot be worked around and the feature (in ControlPlane) will need to go away.

@dreammaker
Copy link

That's sad to hear. This one feature is the reason I sought out and found ControlPlane. I'd be happy to help any way I can to keep this feature, but I'm not familiar with the relevant APIs and wouldn't really know where to begin.

@tharwan
Copy link

tharwan commented Feb 7, 2017

I could imagine if we all file a bug at Apple we might have a chance of either getting it fixed or a definite answer. I mean it is a valid Apple Script to set/unset the checkmark, but then nothing happens, which is clearly a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests