Currently Being ModeratedSep 24, 2012 7:00 PM (in response to Ery-loon)
This has happened to me as well but my update completed just fine with no errors. No screensaver or sleep, unless I manually force it in either state. I restored my machine twice (from Time Machine) back before the update it everything was worked fine until I installed the update again. "pmset -g" is showing the the powerd process is preventing the computer from going to sleep. I assume this is also causing the screensaver to not start.
Currently Being ModeratedSep 24, 2012 8:22 PM (in response to constantmotion)
Believe it or not, I tried to let the computer sleep and shut down the display, I changed their setting is what I did. The screensaver still would not come on. Finally I decided, just now, to reinstall the update. I proceeded to set the Filevault off, it's decrypting the computer now. I turned off the Firewall......Lo and behold, the screensaver came on.
Now here is the question. Is having the drive encrypted what caused the concern, or the firewall. Again, I had received an error message when the update installed, it said it did not install. When in fact it did. Though, this seems to have corrected the issue, I prefer the files encrypted and the Firewall up.
When it finishes decrypting the volume, I will attempt the update again and see if an error message comes up again. If this works, then I know any and all future updates need to be performed this way and will. Time consuming though it may be.
Hmm, maybe it will fix the external speaker issue I have also, that occured after the update. That is another issue for another topic.
ps, Thank You for trying to help!
Currently Being ModeratedSep 25, 2012 5:38 AM (in response to Ery-loon)
Hmmm. Just checked mine and my File Vault and Firewall is off. I turned on the Firewall, just to see, but to no avail.
Currently Being ModeratedSep 25, 2012 5:54 AM (in response to Ery-loon)
I've found that the screen saver will work once, on a restart. But then afterwards, it will cease to "kick in". So, I don't know if it's been working consistently for you, but the solutions I've found, which include: 1. Reapplying the 10.8.2 update, 2. Restarting 3. Repairing Permissions and Restarting etc.... really only work because of the restart, and in that case, the solutions don't fix the problem but only work once, and then for duration of the Mac uptime, the screen saver fails to work. Can anyone corroborate? Thanks.
Currently Being ModeratedSep 26, 2012 2:42 PM (in response to Mark Jenkinson)
Found a solution that seems to have permenantly fixed things:
I put my mac to sleep and then woke it.
I know that sounds like a crazy solution, but this particular Mac had both the display and the Mac set to NEVER sleep. By simply putting the mac to sleep once (and probably never again)...the problem has now been solved.
Currently Being ModeratedSep 26, 2012 6:28 PM (in response to Ery-loon)
Glad to hear you got it going again.. No more Sad Mac. Have Fun Jim P
Currently Being ModeratedFeb 21, 2013 11:31 AM (in response to Ery-loon)
In this forum many ppl including me are discussing the same issue as you are describing here.
For me the issue is for a Mac mini late 2009 running 10.8.2 (upgrade to 10.8.2 made the problem appear). The issue are invoked when i use VNC to access the Mac mini wich leaves powerd preventing Idle Display sleep. Running 'pmset -g assertions' without the ' and scrolling upwards reveals a 1 after PreventUserIdleDisplaySleep. Killing that process makes the screensaver work again until next time I login to the computer via VNC.
Currently Being ModeratedMar 15, 2013 1:15 AM (in response to eriksson.e)
Upgrade to 10.8.3 seems to have solved my issue.
powerd no longer prevents screensaver from starting after screensharing to my Mac mini.