Screen Saver on 10.8.2 Fails to Activate

Unfortunately, I'm not sure how to roll back your update.

This is a frustrating problem that nobody seems to have any luck with.

I have been on the phone with Apple tech 3 times over the last few months with no solution.

At this point, unless someone discovers a fix, I'm going to wait and hope for a fix when 10.8.3 is released.

In the meantime, if everyone would continue to send feed back to Apple on this, maybe we can be the squeaky wheel.

Go to: http://www.apple.com/feedback/macosx.html

#1...did you try changing your hot corner to a different corner. I know it sounds crazy but that seemed to fix my issue.

#2...something I also thought about that might have been the issue is that Mac has the option to make the screensaver operative after 1 minute...I changed it to 5 minutes and changed my hot corner and I haven't had any problem since then. It may have been a fluke but it worked for me. Perhaps the 1 minute option is where the bug is. Just a thought.

I read somewhere (can't find the link) a suggestion that repairing disk permissions within Disk Utility might fix this problem. I tried it a few days ago and my screensaver has been functioning properly since! Worth a shot.

Yea very annoying, i read any another thread some other dudes issue and and he was given the idea to go into terminal and type

pmset -g assertions

this shows what is runnign in the background that is disabling the screensaver. for me it was a audio pass through app called "soundflower" i was using it so i could control my hdmi monitor through the keyboard controls and not have to rely on the the volume controls on the monitor. unistalled soundflower and restarted and screensaver working. I'm am sceptical though bc i had soundlfower installed and would try other things and the screensaver would work again breifly. ill keep yall updated if it goes again. heres the post i found with this suggestion

https://discussions.apple.com/thread/4449324?start=0&tstart=0

oh ya i also disabled wake on lan access. too read that, that was also and idea.

I, too, wish Apple would get this problem resolved. Mine worked for two days after a couple of restarts this past week. Quit working again. Don't know why it is taking so long to get this resolved.

any one try typing

pmset -g assertions in terminal yet?

since doing this ive yet to have a problem. ive actually been trying to nreak it and cant. But i install the soundflower app I was talking about it kills the screensaver. Just wondering if this worked for anyone else

I haven't ever used anything called soundflower so that is not the problem.

No I meant typing that command in terminal will show you, if any, programs running in background that are preventing the screensaver from working properly. In my case it was a program called soundflower.

This is what I get when I do a pmset -g assertions.....I have no idea what anything means. I am running an external montior (HDMI to a TV).

pmset -g assertions

2/24/13 7:37:30 PM CST

Assertion status system-wide:

PreventUserIdleDisplaySleep 1

CPUBoundAssertion 0

PreventSystemSleep 0

PreventUserIdleSystemSleep 1

ExternalMedia 1

DisableLowPowerBatteryWarnings 0

UserIsActive 0

ApplePushServiceTask 0

BackgroundTask 0

Listed by owning process:

pid 154(coreaudiod): [0x0000000100001f2e] 00:29:46 NoIdleSleepAssertion named: "com.apple.audio.'AppleHDAEngineOutputDP:0,1,1,1,0:0:{3A59-0070-01010101}'.noid lesleep"

pid 154(coreaudiod): [0x0000000500001f2f] 00:29:46 NoDisplaySleepAssertion named: "com.apple.audio.'AppleHDAEngineOutputDP:0,1,1,1,0:0:{3A59-0070-01010101}'.nodi splaysleep"

pid 17(powerd): [0x000000050000015a] 17:34:01 PreventUserIdleDisplaySleep named: "com.apple.powermanagement.delayDisplayOff" (timed out)

Timeout will fire in: -62941.9 Action=TimeoutActionTurnOff

pid 17(powerd): [0x000000090000012c] 99:45:17 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"

Kernel Assertions: 0x0012

* Kernel Assertion ID = 500

Created At = 12/31/69 6:02:59 PM CST

Modified At = 2/23/13 9:35:17 AM CST

Owner ID = 0xffffff8013b0c000

Level = 0

Assertions Set = None (4)

* Kernel Assertion ID = 501

Created At = 12/31/69 6:03:15 PM CST

Modified At = 2/20/13 3:58:49 PM CST

Owner ID = 0xffffff8013b59000

Level = 255

Assertions Set = None (4)

* Kernel Assertion ID = 502

Created At = 2/20/13 4:02:13 PM CST

Modified At = 12/31/69 6:00:00 PM CST

Owner ID = 0xffffff8013b68800

Level = 255

Assertions Set = None (8)

Looks like your power management settings are off. I'm assuming your running a MacBook? Check settings for display sleep. Hard drive sleep, etc. then try screensaver.

The pid 17 is the guilty for the screen saver issue....(com.apple.powermanagement.delayDisplayOff)

However we should find out what triggers the pid 17 to show up....

If you go to terminal and hit "sudo kill 17" then the screensaver issue goes away...

For my case if I I connect to a computer with screen sharing and then go to terminal (to the second computer)'and hit pmset -g assertions then pid 17 is showing up...

When I close the screen sharing then the pid 17 isn't killed automatically (however it should ) ....so the screensaver issue is present...

If i simpy kill it (sudo kill 17) the issue goes away...

Therefore the issue is related with the switches of the com.apple.powermanagement procedure...

Of course we cannot fix it ourselves, since Apple has to recompile the binaries for the powermanagement with the right code...

It's an annoying

Hi

I have the same issue which is related to screen sharing. Quite annoying. I've reported it to Apple using their form for reporting bugs but more people should do so to get their attention.

/Erik

ok So ive almost hit a week now and still no issues. looks like ive fixed my screenssaver issue. any one else have any luck with the using terminal to find the issue? seemed to ork fo rme