Jump to content

Sleep Command no longer works


Recommended Posts

I have setup a hotkey (F15) with the System Command "Sleep". But after upgrading to Mac OS X Yosemite 10.10.4 this no longer works.

 

I've tried other keys with no success. Other System Commands like "Screen Saver" or "Show Trash" working as expected.

 

Any ideas to solve this.

 

Thanks

Thomas

Link to post
Share on other sites

I have setup a hotkey (F15) with the System Command "Sleep". But after upgrading to Mac OS X Yosemite 10.10.4 this no longer works.

 

I've tried other keys with no success. Other System Commands like "Screen Saver" or "Show Trash" working as expected.

 

Any ideas to solve this.

 

Thanks

Thomas

 

Hi Thomas,

 

I'm on the same version of OS X and the Sleep command works as expected. Have you restarted your Mac since installing 10.10.4? Sometimes updates just need a bit of smoothing over before OS X responds as expected. 

 

If you launch Console.app and type the "sleep" command into Alfred instead of using your hotkey, does it work? If not, do you see an error message in Console?

 

Cheers,

Vero

Link to post
Share on other sites

Hi Vero,

 

thanks for your reply.

 

There's an error in Console:

osascript[79129]: Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: "/Library/ScriptingAdditions/SIMBL.osax"

 

I have SIMBL installed because I use the SafariStand plugin which give me favicons in Safari tabs and daily download folders. Will probably in the future have to do without it.

Edited by tmconnect
Link to post
Share on other sites

Hi Vero,

 

thanks for your reply.

 

There's an error in Console:

osascript[79129]: Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: "/Library/ScriptingAdditions/SIMBL.osax"

 

I have SIMBL installed because I use the SafariStand plugin which give me favicons in Safari tabs and daily download folders. Will probably in the future have to do without it.

 

SIMBL can do some strange things to your Mac. If you disable SIMBL, do you get the expected behaviour again? 

Link to post
Share on other sites
  • 8 months later...

I have the same problem. While all other System Commands work, I can't get the "Sleep-Command" to work. I don't know when this startet or if it's related to an update, but please help me to solve that problem.
The Console tells me:

System Events[2719]: A call to OSACopyScriptingDefinition() by NSScriptSuiteRegistry returned an error. Is this application's OSAScriptingDefinition Info.plist entry valid? If its value is 'dynamic', is there an 'ascr'/'gsdf' Apple event handler registered?

Link to post
Share on other sites

I have the same problem. While all other System Commands work, I can't get the "Sleep-Command" to work. I don't know when this startet or if it's related to an update, but please help me to solve that problem.

The Console tells me:

System Events[2719]: A call to OSACopyScriptingDefinition() by NSScriptSuiteRegistry returned an error. Is this application's OSAScriptingDefinition Info.plist entry valid? If its value is 'dynamic', is there an 'ascr'/'gsdf' Apple event handler registered?

 

 

Have you tried restarting your Mac to check OS X hasn't got itself into a muddle? This seems like an odd error message and not one that's been reported before.

Link to post
Share on other sites

Have you tried restarting your Mac to check OS X hasn't got itself into a muddle? This seems like an odd error message and not one that's been reported before.

Yes, but restarting doesn't solve the problem  :( 

Any other suggestions? Maybe I should try to delete the .plist (not that I know which one) that is mentioned in the error message?!

Link to post
Share on other sites

Yes, but restarting doesn't solve the problem  :( 

Any other suggestions? Maybe I should try to delete the .plist (not that I know which one) that is mentioned in the error message?!

 

 

It's not recommended to arbitrarily delete .plist files - While some .plists are re-created dynamically, there are many that aren't re-created and could cause more serious issues on your Mac. As this isn't an Alfred-related file, I can't advise as to what would happen.

 

Try creating a new user account on your Mac and try the same action. Does it work as expected? This will help you establish whether the issue is across your Mac or specific that your user profile.

 

Cheers,

Vero

Link to post
Share on other sites

It's not recommended to arbitrarily delete .plist files - While some .plists are re-created dynamically, there are many that aren't re-created and could cause more serious issues on your Mac. As this isn't an Alfred-related file, I can't advise as to what would happen.

 

Try creating a new user account on your Mac and try the same action. Does it work as expected? This will help you establish whether the issue is across your Mac or specific that your user profile.

 

Cheers,

Vero

I tried this with a guest account and it didn't work. So I guess it's an issue across the Mac. Could that help in finding a solution?

Thank you for your precious time and happy easter greetings from Rostock / Germany. :)

Link to post
Share on other sites
×
×
  • Create New...