Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.5: Avoid a direct screen saver activation issue System 10.5
In previous versions of the Mac OS, an easy way to activate the screen saver was to trigger the ScreenSaverEngine application. In 10.5, though, there appears to be an issue with this technique.

If you also have the screen saver to come on after a set amount of time, the screensaver will dutifully activate at that time, even if it is already active. This results in some very interesting visuals, and a lot of GPU-churning as two copies of the screen saver vie for attention.

One solution I've found for this -- a technique that still allows you to put an executable in your dock, create a keyboard shortcut, etc., -- is to simply create an Automator action to activate the screensaver. Just open Automator, select Custom, select the Utilities category, and create a workflow consisting of the Start Screen Saver action. Save this workflow as an application, and you now have a tiny application that will activate the screen saver when clicked. Screensavers activated in this way do not seem to suffer from the double-saver syndrome.
    •    
  • Currently 3.00 / 5
  You rated: 5 / 5 (4 votes cast)
 
[15,897 views]  

10.5: Avoid a direct screen saver activation issue | 8 comments | Create New Account
Click here to return to the '10.5: Avoid a direct screen saver activation issue' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Avoid a direct screen saver activation issue
Authored by: cuban321 on Nov 15, '07 03:29:59PM

I'm guessing this bug is why coreservicesd eats up hundreds of megs of ram. I use the ScreenSaverEngine trick all the time. I'll try the automator one and see if it makes a difference. Thanks!



[ Reply to This | # ]
10.5: Avoid a direct screen saver activation issue
Authored by: cuban321 on Nov 26, '07 07:04:09AM

nope, no difference. :(



[ Reply to This | # ]
10.5: Avoid a direct screen saver activation issue
Authored by: KeithGarner on Nov 15, '07 03:47:01PM
If you're using something like RandomExtra it gets really trippy when you have two different screen savers fighting over the screen.

I had thought RandomExtra was the culprut, but it looks like my use of Salute might be. Thanks for clearing this up, this was really annoying me.

[ Reply to This | # ]

10.5: Avoid a direct screen saver activation issue
Authored by: dangriffin on Nov 15, '07 05:19:17PM

Why not just use hot corners? I just move the mouse cursor to the lower left corner and boom, screen saver starts. Move it to the lower right and it's disabled.



[ Reply to This | # ]
10.5: Avoid a direct screen saver activation issue
Authored by: q-wert on Nov 15, '07 08:14:55PM

In my case, I've set it so that my password is needed to exit Screen Saver… in this case, I have zero tolerance for accidental activation of hot-corners. (Accidentally activate Screensaver, enter password,… <repeat>)

I have the Script Menu enable and, amongst others things, had a script to "Lock the Screen".

Thanks for the Tip!! :-D



[ Reply to This | # ]
10.5: Avoid a direct screen saver activation issue
Authored by: skinnyjimmy on Nov 16, '07 02:58:37AM

Thanks for this hint - that is exactly the cause of the stuttering screen saver syndrome (for me, anyway), and the fix works perfectly!



[ Reply to This | # ]
10.5: Avoid a direct screen saver activation issue
Authored by: Jon on Nov 16, '07 04:29:43AM

There is a better way to launch the sceen saver:
Activate the Keychain menu item from Keychains preferences. In that menu you can choose "Lock screen".

But – and this is a related tip – if you have screen password protection on, you should shut off the screensaver itself and instead rely on the energy saver screens sleep (black screen). At least if you want immediate access to your desktop when the computer wakes up from sleep and you have entered your password. That is: The black screen sleep function is activated instead. Otherwise you are likely to get the wellknown problems with long delays (or worse).

Screensavers is maybe nicer to look at, but the black screen works much better if you want password protection.



[ Reply to This | # ]
10.5: Avoid a direct screen saver activation issue
Authored by: buckthorn on Mar 20, '08 05:10:04AM

I think that there is still an issue with activating the screensaver via Automator. I've set up an Automator app using the "Start Screen Saver" action, and my logs show that the bug with coreservicesd is alive and well (I'm using an early 2008 Mac Pro, 10.5.2):

------------------------------------------
Mar 19 15:58:06 booker ScreenSaverEngine[832]: argument '-psn_0_409700' not understood
Mar 19 16:41:52 booker com.apple.coreservicesd[58]: coreservicesd(58,0xa05defa0) malloc: *** mmap(size=16777216) failed (error code=12)
Mar 19 16:41:52 booker coreservicesd[58]: coreservicesd(58,0xa05defa0) malloc: *** mmap(size=16777216) failed (error code=12)\n*** error: can't allocate region\n*** set a breakpoint in malloc_error_break to debug
Mar 19 16:41:52 booker com.apple.coreservicesd[58]: *** error: can't allocate region
Mar 19 16:41:52 booker com.apple.coreservicesd[58]: *** set a breakpoint in malloc_error_break to debug
Mar 19 16:41:52 booker ReportCrash[853]: Formulating crash report for process coreservicesd[58]
Mar 19 16:41:52 booker ReportCrash[853]: Saved crashreport to /Library/Logs/CrashReporter/coreservicesd_2008-03-19-164152_Booker.crash using uid: 0 gid: 0, euid: 0 egid: 0
Mar 19 16:41:53 booker com.apple.launchd[1] (com.apple.coreservicesd[58]): Exited abnormally: Bus error
Mar 19 16:41:54 booker /Applications/Microsoft Office 2008/Office/Microsoft Database Daemon.app/Contents/MacOS/Microsoft Database Daemon[301]: LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.
Mar 19 16:41:54: --- last message repeated 1 time ---
Mar 19 16:41:54 booker ReportCrash[854]: Formulating crash report for process ScreenSaverEngine[842]
Mar 19 16:41:55 booker WindowServer[61]: LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.
Mar 19 16:41:55 booker ReportCrash[854]: Saved crashreport to /Users/pweil/Library/Logs/CrashReporter/ScreenSaverEngine_2008-03-19-164152_Booker.crash using uid: 501 gid: 501, euid: 501 egid: 501
Mar 19 16:41:55 booker com.apple.launchd[86] ([0x0-0x68068].com.apple.ScreenSaver.Engine[842]): Exited abnormally: Bus error
Mar 19 16:41:55 booker WindowServer[61]: LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.
Mar 19 16:41:55 booker /System/Library/CoreServices/UserNotificationCenter.app/Contents/MacOS/UserNotificationCenter[859]: _RegisterApplication(), FAILED TO REGISTER PROCESS WITH CPS/CoreGraphics in WindowServer, err=-50
---------------------------------

and on and on



[ Reply to This | # ]