gungholady, have you just installed 10.8.2 or have you had it for while and the problem only just started?
I check every day - just in case there is an upgrade available.
I sometimes forget to turn on the screensaver after use (hot corners) and my mac is left all day with the image just burning into the screen. It is getting annoying now - time for a fix.
I suppose it is time for yet another feedback email, boring.
The problem just started about a week ago. I don't remember any major updates since I bought my system in October. Yes, I agree with you that it is annoying especially for me since the problem just started. If I restart and don't spend time on the computer, it works. If I have to use it for several hours, then it stops working again.
think Apple did not even look at this forum, and so it is not resolved,
I have the problem from day 1 that the update came out, then you can expect that the problem is solved after all these months,
But no, Apple is not working on a solution,
I think I'm going to install Lion again, in the hope that it is resolved, and that my screensaver is working,
Just thought I'd throw my hat into the ring as well. I have a Mac Mini in our media center driving a plasma TV, and the screen saver recently failed to activate (I had it set to 1 minute to prevent plasma burn in). For me, the problem just started a few days ago, although I updated to OS 10.8.2 about 2 weeks ago. Strange. This morning, after booting the computer, the screen saver didn't even start the first time. Like many of you, the more typical scenario is that is works normally the first time, then fails to activate on subsequent inactivity.
I tried the suggested trick of adding another Administrator account to the Mini, but that made no difference.
I'll leave some feedback to Apple to raise visibility to this annoying issue and check back here.
I filed another complaint with Apple about this yesterday. From my searches on the internet regarding this problem, it appears that the screensaver has been an issue with Apple systems for a number of years. I have used PC's with Windows and Linux for years and have never had a problem with the screensaver not starting until I got this Mac Mini.
I can only speak for myself.
I've been using Apple/Mac computers for over 20 years. Never had a screensaver problem until 10.8.2.
Recently I download Living Earth HD from the app store and I'm using it as a screensaver.
I'll use L E HD until Apple gets around to fixing this.
Merry Christmas or Happy Holidays (pick the one you prefer) to all!
GungHo Lady, I have no doubt that there have been problems with almost any aspect of the Mac OS with some individuals since the beginning of time (at least since early 1984 when I first started using a Mac). Like corvair kid (and most other on this tread), I have had no problem with this issue until 10.8.2, so I doubt if this specific problem is related to issues you found documented earlier. Like you, I also have used (and continue to use) Windows and Linix/Unix at work for over twenty years and have no recollection of a screen saver problem on those platforms. However, I have had an incredible list of far more critcal issues with both Windows & Linux. There really is no comparison in the stabillity of OS X and Windows, and to a lesser degree, Linux. On the other hand, Unix is incredibly stable, but then again, it means you have to use Unix ;-)
Glad you are complaining to Apple... I urge everone on this thread to contact Apple at:
The problem is with a process inappropriately requesting that display sleep not be allowed via power assertions (paragraph 4). You can view all power assertions in the Terminal by executing the command
pmset -g assertions. You'll see a quick summary of the types of power assertions active at the top, but for this issue, we're mainly interested in
PreventUserIdleDisplaySleep. For instance, when I'm playing a movie in iTunes, I don't want my display to sleep.
In my case, I've seen processes like helpd requesting this power assertion which prevented my screensaver from activating. Simply kill the process to have your screensaver work again (
I'm playing a movie in iTunes now, so when I run pmset -g assertions, I see the following near the top of the output:
pid 34172(iTunes): [0x000000010000257e] 00:00:06 PreventUserIdleSystemSleep named: "Nameless (via IOPMAssertionCreate)"
pid 34172(iTunes): [0x000000050000257d] 00:00:07 PreventUserIdleDisplaySleep named: "Nameless (via IOPMAssertionCreate)"
iTunes is preventing both system and display sleep. If I pause the video, those two assertions go away.
Living Earth HD has it's own screensaver. It's a really nice revolving planet earth which is updated periodically to show day, night, and current cloud formations. You can set it to activate in from 3 minutes to 2 hours or Never.
To run it you need to disable your system screensaver (put it to "Never") and set your display sleep time to start later than the Living Earth screensaver. Unfortunately it does not activate the screen lock. I have my screen lock set for when my display goes to sleep.
I have another question regarding the "screen-lock with display sleep". It sounds like your "screen-lock on display sleep" works? Mine doesn't and I assumed it was for the same reason the screen saver doesn't activate. Ninty percent of my desire to fix this isuue is to have the computer "lock itself" after a period of inactivity. I don't really care (as much) if it is through "screen sleep" or "screen saver" activation.
Perhaps you can clarify this for me. I may have two problems instead of just one!