Security problem: Waking from screen saver botched in 10.5.5

When using my MBP, I like to have my screen saver as simple computer lock in that it requires a password to wake the computer from sleep or screen saver (option in the Security system preference pane).
Since the update to 10.5.5, my computer just wakes from sleep or when in screen saver mode, without demanding a password to be entered, even though the option is checked in the pane. I did an immediate SMC reset after the installation because the fans were acting oddly, and a PRAM zap just now to see if it'd do any good with this problem.
Has anyone experienced something similar?

I had this happen a few times back when I was running Tiger. I was able to fix it by going to Homefolder/Library/Preferences/ByHost and deleting all of the com.apple.screensaver.xxxxxxx plist files, and then logging out/in.

Similar Messages

Missing password window when waking from screen saver

I've had some issues with waking from sleep once I turned on the screen saver password. I opened the lid and the screen lit up and I had the mouse pointer--but no user name/password box.
I tried opening/closing the lid a few times, plugging it in to an external monitor, etc, and no luck. I ended up having to hold the power key down until the machine turned off and then I rebooted, and I lost some work.
Is there any way to force a login screen?

I have a simple solution, go to your "Energy Savings" setting under the System Settings, once there move the slider-bar so that your screen saver is never activated. Now move the slider-bar so the system goes into "stand-by" mode after 5-10 minutes, thus once opened again, should prompt you to enter your password..?!
Please ignore the "Windows" terms. I'm a new Mac user, but this solution has seamed to work in my case, at least until a "Fix" is made.

Dock disappears when waking from screen saver

I have had this happen a couple of times. It's an intermittent problem that I haven't found a pattern for yet.
When coming out of screen saver, the dock has vanished. The dock process doesn't show as hung and seems to be behaving normally. If I kill the process, it restarts and the dock launches properly and is fully functional.

Fixed in update.

Resume from Screen Saver Issues

Hey All,
Well...migrated from Leopard to Snow Leopard with minimal issues but
In Leopard, after waking from screen saver, a box would prompt for a password. I've gotten SL to do this, but there is no way to switch user.
I have multiple users and i'm unable to switch users from SL.
Any ideas??
Kayle

Hey All,
Well...migrated from Leopard to Snow Leopard with minimal issues but
In Leopard, after waking from screen saver, a box would prompt for a password. I've gotten SL to do this, but there is no way to switch user.
I have multiple users and i'm unable to switch users from SL.
Any ideas??
Kayle

Gray Background of Login Screen After Returning from Screen Saver

I'm setting require password after sleep or screen saver begins
When awaking from sleep
login screen background is blur wallpaper ( correct ),
but when return from screen saver
login screen background is gray ( incorrect )
how to fix it?
Answer Similar Question
http://www.cnet.com/news/os-x-desktop-backgrounds-gray-after-waking-from-sleep/
I try to solve it,
but it dose not any effect.
Now I will updating OS X to v10.10.3
but I think the problem is still there.
MacBook Pro , OS X Yosemite v10.10.2

right, i'd just like to add that this issue was solved by installing "proper" ati drivers, or lowering sync and refresh rates in /etc/X11/xorg.conf, one of those

Lacie Speakers and Mac Pro Firewire problem waking from sleep and loud feed

Lacie Speakers and Mac Pro Firewire problem waking from sleep and loud feedback. I had a powermac before this with the speakers and it worked fine. But the mac pro is having these issues. Is it the firewire port or the speakers or (and most likely) just a firmware glitch with mac pro? Anyone else see these issues?

http://web.mac.com/jerimydulay/Site/MyAlbums/Pages/Lacie_FirewireMIDI.html
Here is my audio settings. For some reason I wish I could remember what I did. It was actually the Apple Store tech in the Unversity Village in Seattle that gave me the idea and I swear I had to change the settings in MIDI setup. Now that Leopard is out it seems the MIDI stuff has been redone. I included screenshots of my MIDI setup as it is currently to see if you see something different on your computers. Let me know!

HUGE SECURITY HOLE IN LOGIN FROM SCREEN SAVER

One of the options in the security panel permits a user to require that a username and password be entered to login once the screen saver locks your account.
The option is "Require password to wake this computer from sleep or screen saver"
Although one would assume that the credentials required to wake the computer is the username/password of the account that was being used when the computer went into sleep mode or the screen saver. WRONG!!! Anyone with an account on the machine can enter their username/password and wake the computer and voila that user now has control of the machine as the former user. That's right you guessed it HUGE security hole.
Anyone thinking that they can wake away from their machine and have the screen saver or sleep mode protect their account after a specified period of time is sadly mistaken. Anyone with an account on the machine can enter their own username and password and drop right into your account right where you left off.
Can you believe this stuff? No warning, no release note to tell you of such a poorly designed "security" option.
Apple please fix what must have been an oversight or at least tell people about this intentional design BEFORE they find anyone can wake the computer and become you as a user.
Thanks,
JH

jonathan_2005 wrote:
One of the options in the security panel permits a user to require that a username and password be entered to login once the screen saver locks your account.
The option is "Require password to wake this computer from sleep or screen saver"
Although one would assume that the credentials required to wake the computer is the username/password of the account that was being used when the computer went into sleep mode or the screen saver.
Never assume
WRONG!!! Anyone with an account on the machine can enter their username/password and wake the computer and voila that user now has control of the machine as the former user. That's right you guessed it HUGE security hole.
Anyone with a standard user account? Are you quite sure?
Anyone thinking that they can wake away from their machine and have the screen saver or sleep mode protect their account after a specified period of time is sadly mistaken. Anyone with an account on the machine can enter their own username and password and drop right into your account right where you left off.
I never think that way. A more secure lock is ensured by using the screen lock feature of the keychain.
Can you believe this stuff?
Not sure what stuff you refer to.
No warning, no release note to tell you of such a poorly designed "security" option.
Would you believe that anyone can access your computer? Stolen computers are regularly started up without much problem.
Apple please fix what must have been an oversight or at least tell people about this intentional design BEFORE they find anyone can wake the computer and become you as a user.
You are writing to other users like yourself here, not Apple.
I also presume you are new to the Mac world.

Spinning beach ball when waking up from screen saver or sleep

A few months ago, my ancient (Quicksilver G4) Mac started giving me a spinning beach ball for a few seconds every time I wake it up from sleep or from the screen saver. It lasts anywhere from about 5 to 20 seconds. It never used to do this. The problem has continued despite a recent upgrade form 10.3.9 to 10.4.10. Repairing permissions and resetting PRAM hasn't helped. Any ideas?

Well... I tried many of those things in the search results, and nothing changed initially... i.e. after changing desktop backgrounds (which is all it seemed to take on my mini), and then changing passwords, I continued to not be prompted for my password until I restarted. Logging out might've worked as well, but I just went gung ho and went right for the restart.

MBP switches spaces when returning from screen saver

When I move my finger minimally across the touchpad to bring my screen out of screen saver, invariably my MBP decides to shift spaces to the next to the left or right.
It is annoying.

From System Preferences, go into Security. Hopefully, the padlock icon at the bottom will show as unlocked, because if it doesn't you need a password to open it to allow you to make changes. You will see a box that says "Require password to wake this computer form sleep or screen saver." That should do it. The password being asked for is your administrative password.
Maxit

10.9.4 not responding when logging in from screen saver

I have a MacBook Air with Mavericks and this wee I updated to 10.9.4. I have password activated restart from screensave; everything was normal but today, when I close the display and it sleeps, at the start screen I type my password and it freezes, it does not log in or does anything else, the dots showing representing the password go grey and ceases working. If I press the power button it restarts the login screen but after typing the password it does the same. If you type the wrong pass it shakes and says bad password so it responds to that but does not login.
If I force a restart, at the login screen it accepts the password and logs in but not after sleep or screen saver. Any ideas? I deactivated the password protected screen saver but it is not a solution, I hope you could help me.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Problem in MIT-SCREEN-SAVER

I'm using beforelight (v1.3) from XFree86. This program uses MIT-SCREEN-SAVER for screensaver event. It works fine under 5.6, and 5.8 if built with 32-bit. But after I rebuilt it with 64-bit (add -xarch=v9a in Makefile) and ran the binary, I got a core dump in the function XScreenSaverSelectInput(). Workshop reports invalid address alignment in XScreenSaverSelectInput at 0xffffffff7e510108. What could be the problem?

Tested with a simple program, main() does nothing but initializing MIT-SCREEN-SAVER and starting a eventloop listening for screensaverevent. The initialization code is:
int main(argc, argv)
int argc;
char **argv;
Widget toplevel;
XEvent event;
XScreenSaverNotifyEvent *sevent;
XID               kill_id;
Atom          kill_type;
toplevel = XtAppInitialize (&app_con, "Beforelight", NULL, ZERO,
                    &argc, argv, NULL, NULL, ZERO);
display = XtDisplay (toplevel);
root = DefaultRootWindow (display);
screen = DefaultScreen (display);
if (!XScreenSaverQueryExtension (display, &ss_event, &ss_error))
          exit (1);
if (XScreenSaverGetRegistered (display, screen, &kill_id, &kill_type))
          XErrorHandler old_handler = XSetErrorHandler (ignoreError);
          XKillClient (display, kill_id);
          XSync (display, 0);
          XSetErrorHandler (old_handler);
XScreenSaverSelectInput (display, root, ScreenSaverNotifyMask);
XSync (display, False);
XSetScreenSaver(display, MyTimeout, 0, 0, 0);
eventloop();
This works fine when linked with 32-bit, but crashed (sometimes report BadDrawable) in XScreenSaverSelectInput(). I'm wondering if the 64-bit MIT-SCREEN-SAVER doesn't work properly.

Sign in from screen saver

I am having trouble with my Mac accepting my password from the screen saver. What happens is that when I enter my password into the screen saver it gets hung up and doesn't move past that point. Each time this happens I basically have to reboot my system. I use my Mac as a corporate machine so I'm assuming this is some kind of authentication problem with my credentials?

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Problems with Mavericks screen saver

I downloaded Mavericks on Saturday. On Sunday after the download was completed my screensaver from my IPhoto library was replaced by a blue "wave" shot which is one of the default screens on the new OS. I tried to reload my photo as a screensaver with no success. I spent 3 hours with Apple Support and three different support representatives. All unsuccessful. It would appear that the Mavericks OS will only allow you to use one of the Apple default screens as the screen saver. Has anyone else experienced this problem? In my old OS one simply clicked on system preferences, then screensavers and you chose a photo from the list of Apple landscapes, etc or a photo from the IPhoto library. That option seems not to exist any longer. Welcome comments by new Mavericks users.

Yes, I have the same issue.

15" MBP screen has blue tinge after wakeup from screen saver

I've had a recent problem with having a blue tinge to my laptop display after wake up from the screen saver. The screen saver is the iTunes cover art. When the screen saver is active and I clear it (mouse movement or keyboard), I get my login screen. After entering my password, the screen turns a blue shade. Does anyone else have this problem or know of a solution. I'm currently running Leopard 10.5.8 with all software updates on a late 2008 15" MBP.

Yea I had this problem a while ago - I think it's because of iStat Pro - are you running that widget in your dashboard? Either delete it or if you still want it - you can go into preferences and click on displays and the screen will automatically color correct itself - but you have to do this every time it wakes up.

Fast User Switching From Screen Saver

How can I make my Mac display the login screen (as though I'd selected "Login window" from the fast user switching menu) after the session has been idle for a certain time?
I can make it log out after some amount of inactivity, but I don't want that. I want my programs to continue running.
I can also set the screen saver to require a password, and clicking the "Switch user" button on the password dialog will display the login screen. I'd effectively like to skip that step and go directly to the login screen without having to push the button.
note: I stole the wording of this question directly from here , which was posted 2 1/2 years ago. One solution then was to download a custom Script Saver and use a custom Apple Script, and the other was to purchase a 3-rd party product which costs $50.
The reason I want to do this is because I am setting up an iMac for a family with small children. The iMac will be shared by 4 people, and training the kids to click on the "Switch User" button is a hopeless task, so please don't suggest "train the users to click on the 'Switch User' button".
Also, this is not my computer. I want to keep the solution as simple and fool-proof as possible, becuase I don't want to get called if something breaks (which is why I'm disinclined to use a script or buy a 3-rd party product I don't trust).

PS -- Script Saver has been discontinued.
https://www.macupdate.com/app/mac/9599/scriptsaver
So that's not an option anyway.

Security problem: Waking from screen saver botched in 10.5.5

Similar Messages

Maybe you are looking for