This discussion is archived
12887 Views 4 Replies Latest reply: Jan 19, 2010 12:58 PM by Marco M.
Currently Being ModeratedOct 6, 2009 1:53 PM (in response to Richard Collyer1)Got the same problem here.
Seems I got rid of it by updating my LaunchServices database :
1) Open the Terminal, and log in with an admin account (by using su and/or sudo for example) if your current OSX account does not have admin privileges.
2) Go to the LaunchServices.framework' Support directory :
*cd /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.fra mework/Support*
+(Note: in previous OSX versions, it was a subframework of ApplicationServices and not CoreServices, the path has changed since)+
3) Use the "lsregister" commande line tool found in this directory to do a rescan/rebuild of your LaunchServices database. You can e.g. update your whole database with this command :
*./lsregister -r -apps local,system,user*
+(Or you can specify the path to the ScreenSaverEngine.app itself directly as a parameter)+
After the LaunchService database has been rebuild, you should be good with ScreenSaverEngine (you can use an active corner to launch it immediately and check if the fix worked).
HTHMacBook Pro, Mac OS X (10.6.1)
Currently Being ModeratedDec 29, 2009 10:47 PM (in response to AliGator35)I'll confirm AliGator35's fix.
Running "./lsregister -r -apps ScreenSaverEngine.app" in the directory referred to above fixed the problem. Still don't know how I broke it though.Mac Pro, MacBook Pro