Currently Being ModeratedOct 10, 2012 2:52 PM (in response to Len Gold)
This is in reply to your self-reply about going back to the prior version and it still not working...
I should have mentioned in my original post, I never upgraded to 10.8.2 (although keep in mind I've only had my mac for a week), so honestly I'm not sure it has anything to do with the newest version in and of itself. There's something else going on here.
For people having this problem, what exactly happens in your situation? For me, the screen just goes blank as opposed to my chosen screen saver activating. I have my settings such that after a minute of the screen saver running, it prompts for a password. This still happens after a minute of my screen being blank (i.e., the non-screen saver, not MY screen saver).
For the rest of you... does your screen go blank when the screen saver is supposed to activate, or are you not even getting a blank screen?
Currently Being ModeratedOct 10, 2012 3:41 PM (in response to NumbersGirl271828)
I would say you don't have the same problem. Nothing happens on mine when the screensaver is supposed to activate (and I assume others on this thread). The desktop remains visible.
I would be happy if mine worked like yours. I really only want the lock screen to come on for security reasons. I don't really care if a specific screen saver comes on (although I understand that it is annoying that you can't select the one you want).
Currently Being ModeratedOct 11, 2012 6:25 AM (in response to David Strait)
Yes, I restarted a few hours after making the change.
I'm not optimistic on how long it's going to work.
What irks me is that we are all setting and resetting various things to try to solve this... the darn thing should work no matter what the settings are at.
What we need is a bug fix from Apple.
Currently Being ModeratedOct 11, 2012 8:11 AM (in response to corvairkid)
Screensaver still working, but now I have a new issue.
When I change the Desktop Background, it doesn't save.
I can change the background, but after restart, it reverts back to the background that was on the computer when I purchased it last July.
Anyone having this problem?
I am starting a new thread for this.
Currently Being ModeratedOct 11, 2012 9:37 AM (in response to corvairkid)
I just got off the phone with Apple and the tech had me do the following. According to him the 2 problems were related.
Here is a list of procedures we went through:
- Navigated to ~/Library
- From /Preferences, deleted:
- Deleted contents of Library/Saved Application State folder
- Emptied trash, restarted computer
Hopefully this is the final solution.
Currently Being ModeratedOct 11, 2012 11:06 AM (in response to corvairkid)
Did all that in the early days, that is the third peice of conflicting advice from Apple, none of which work. The chap I spoke to a while ago at Apple just suggested a complete re-install (which I did) and report feedback to Apple if it didn't work (which I did).
Currently Being ModeratedOct 16, 2012 2:49 PM (in response to Sjamex)
I am experiencing the same problem in 10.8.2
I have found that the problem for me is appearing after using the screen sharing....
You can find out what process makes the screensaver not to kick in by typing in terminal the command...
pmset -g assertions
For me it's like this (after closing the screen sharing connection)
% pmset -g assertions
Assertion status system-wide:
pid 18(powerd): [0x00000005000001d7] 11:24:18 PreventUserIdleDisplaySleep named: "com.apple.powermanagement.delayDisplayOff"
This means that pid 18(which for me is screensharing) is preventing the screensaver to show up...
So just typing "kill -9 18 "...
solves te problem...!
For my case when the screensharing is invoked then normally it prevents the display to sleep or else for the screensaver to show up...however when you close the screensharing then powerd doesn't get back to the normal state(this is the bug)..so just killing the process the problem is solved...
However it is very very annoying to kill the process after every screensharing session...
So Apple should solve the problem....
You can find out what process makes the same thing for u using te same procedure...
Hope that this helps someone and for Apple solving the problem...