New Lion Login Screen, Auto Sleep?

I set up two user accounts on my Mac Mini 1.83GHZ Core 2 Duo, and each account is set to auto-log off after 10 minutes of inactivity.  This works as expected (phew!) so that when each user needs to use their account, the computer is ready for them at the new log in screen.  Since this Mac is hooked up to a 40" TV, I want to make sure that I dont screenburn my TV if I leave it on at the new login screen.  I waited for ten minutes and the mac didn't sleep at the new login screen, I know I have the option to Sleep it from there manually, but does anyone know if the new login screen was designed to autosleep?
Thanks,
Mr. Louis

I guess I'll try turning off Vault
as per this thread its supposed to fix it.
https://discussions.apple.com/message/15794636#15794636

Similar Messages

  • Adjusting (ok... fiddling) the new Lion login screen

    Is it possible to edit the new Lion Login screen beyond replacing the picture (/System/Library/Frameworks/AppKit.framework/Versions/C/Resources/NSTexturedFul lScreenBackgroundColor.png)?  Specifically, can you change the contrast/brightness of the background picture and more importantly add the hostname/machine name as we had with the original login screen (handy when setting up computer labs).  Does the machine administrator have access to an hidden program to handle this?

    I guess I'll try turning off Vault
    as per this thread its supposed to fix it.
    https://discussions.apple.com/message/15794636#15794636

  • Since upgrading to Lion the screen auto brightness adjusting icon comes on allmost all the time even though i've switched it of in preferences?? it's so annoying..any ideas??

    Since upgrading to Lion the screen auto brightness adjusting icon comes on allmost all the time even though i've switched it of in preferences?? it's so annoying..any ideas??

    I don't know exactly what the issue is, but I think I do. Are you talking about what happens when you start up your MBP, full brightness, with power cable in - and when you're using battery only, the brightness dims? If so, this is a feature designed to make sure your monitor is bright enough while using batteries - but not so bright as to cause an undue drain on power.
    I don't know about a cure to this issue, if indeed this is what you're talking about.

  • Lion login screen problems on Mid 2009 MacBook Pro

    After upgrading my wife's Mid 2009 MacBook Pro from Snow Leopard to Lion we are seeing weird behavior on the login screen after the computer wakes from sleep mode.
    The screen is only partially drawn (usually the top left 1/4 of the screen), and the grey background is shown instead of her desktop background picture. When you move the mouse around on the screen, it repaints blocks on the screen where the pointer has been.
    This only seems to happen when the machine sleeps for a long period of time, e.g., overnight. When it just sleeps for a little while we don't see the issue.
    When searching the forums for anyone else with the problem, several folks said that there was an issue with the video drivers for the 9400M card and recommended switching to the 9600M GT, but her machine only has the 9400M in it.
    All other aspects of the system work fine.
    Anyone else seeing this? Any clues?

    Surprised there hasn't been anyone else experiencing this issue.
    I have seen this on 2 new MBP 2.3mhz i5's with the Intel HD 3000 384mb graphics, Lion 10.7.3 & 10.7.4.
    Also with the latest Lion firmware for the late 2011 MBP's that addresses compatibility and stability issues.
    Hopefully there is a fix soon because the painting on my locked screen to login is getting annoying

  • OS Lion login screen buttons

    I recently upgraded to lion so far most things are ok. I have one issue though, the new buutons on the login screen to shut down and restart don't work. Is anyone else having this issue or know of a way to resolve it. 

    I guess I'll try turning off Vault
    as per this thread its supposed to fix it.
    https://discussions.apple.com/message/15794636#15794636

  • USB devices cause a crash at Lion login screen

    Since I have installed MacOS X Lion I am experiencing regular crashes at the login screen at startup.
    These crashes occur virtually always when
    + a USB device that was connected at the previous shutdown is missing at next launch
    + a USB device that was not connected at previous shutdown is connected at next launch
    The type of the device does not make a difference.
    I have had this with USB sticks, but also with my Wacom graphics tablet and a regular USB hard disk (connected via two USB ports).
    This is extremely annoying and I had hoped this would be fixed with the latest Lion upgrade, but it is not.
    Anyone out there has an idea for an easy fix?

    Guys -
    am I really the only person who sees this?
    This is a serious issue and I also see it happening upon connecting certain USB devices (e.g. today a Garmin nüvi 1250) while running Lion. Non of the OS updates since I posted this helped.
    I feel like I am running Windows here...

  • Why is the resolution of my Lion login screen so low?

    I just turned on my MacBook Air, and I found that the login screen was enlarged, in which it seemed to me that the resolution of the login screen was very low. But after logging in, the resolution went back to normal. How can I fix this?

    So the pictures hardly show a difference, but both my friend and I agree that there is a clear differene the picture quality of my laptop and the monitor.
    Also, the photos are too large to be uploaded here.
    Laptop:
    http://i1131.photobucket.com/albums/m559/AaronAAA/laptop.jpg
    Monitor:
    http://i1131.photobucket.com/albums/m559/AaronAAA/original.jpg

  • Lion login screen hangs

    Hello, this is more of a FYI than a question.
    Symptom: Upon entering your credentials in Mac OS X Lion Server, the login window will hang. However you can still move the mouse.
    Since the Mac's background services were up and running at this point, I could SSH in and look around.
    system.log revealed this:
    Jan 19 18:55:01 Tesseract com.apple.authorizationhost.00000000-0000-0000-0000-0000000186AF[482]: buffer size: 1024 length: 592
    Jan 19 18:55:01: --- last message repeated 1 time ---
    Jan 19 18:55:01 Tesseract loginwindow[461]: Login Window - Returned from Security Agent
    Jan 19 18:55:01 Tesseract loginwindow[461]: USER_PROCESS: 461 console
    Jan 19 18:55:01 Tesseract applepushserviced[103]: Unable to bootstrap_lookup connection port for 'com.apple.iCalPush': unknown error code
    Jan 19 18:55:01 Tesseract applepushserviced[103]: Unable to bootstrap_lookup connection port for 'com.apple.syncdefaultsd.push': unknown error code
    Jan 19 18:55:01 Tesseract applepushserviced[103]: Unable to bootstrap_lookup connection port for 'com.apple.AddressBook.PushNotification': unknown error code
    Jan 19 18:55:01 Tesseract applepushserviced[103]: Unable to bootstrap_lookup connection port for 'com.apple.safaridavclient.push': unknown error code
    Jan 19 18:55:01 Tesseract airportd[499]: _doAutoJoin: Already associated to “Emerald”. Bailing on auto-join.
    Jan 19 18:55:01 Tesseract com.apple.launchd.peruser.501[453] (com.apple.ReportCrash): Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    Jan 19 18:55:01 Tesseract com.apple.launchctl.Aqua[502]: com.apple.RemoteDesktop.agent: Already loaded
    Jan 19 18:55:01: --- last message repeated 1 time ---
    Jan 19 18:55:01 Tesseract com.apple.launchctl.Aqua[502]: load: option requires an argument -- D
    Jan 19 18:55:01 Tesseract com.apple.launchctl.Aqua[502]: usage: launchctl load [-wF] [-D <user|local|network|system|all>] paths...
    Jan 19 18:55:01 Tesseract loginwindow[461]: -[__NSCFConstantString count]: unrecognized selector sent to instance 0x10eeda8e0
    Jan 19 18:55:01: --- last message repeated 1 time ---
    Jan 19 18:55:01 Tesseract loginwindow[461]: (
                                  0   CoreFoundation                      0x000000010ed87286 __exceptionPreprocess + 198
                                  1   libobjc.A.dylib                     0x000000010ebf1d5e objc_exception_throw + 43
                                  2   CoreFoundation                      0x000000010ee134ce -[NSObject doesNotRecognizeSelector:] + 190
                                  3   CoreFoundation                      0x000000010ed74133 ___forwarding___ + 371
                                  4   CoreFoundation                      0x000000010ed73f48 _CF_forwarding_prep_0 + 232
                                  5   loginwindow                         0x000000010c5bf2c9 loginwindow + 74441
                                  6   loginwindow                         0x000000010c5bf293 loginwindow + 74387
                                  7   loginwindow                         0x000000010c5bc646 loginwindow + 63046
                                  8   CoreFoundation                      0x000000010ed76a1d -[NSObject performSelector:withObject:] + 61
                                  9   Foundation                          0x000000010e0a5e44 __NSThreadPerformPerform + 214
                                  10  CoreFoundation                      0x000000010ecf5b51 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
                                  11  CoreFoundation                      0x000000010ecf53bd __CFRunLoopDoSources0 + 253
                                  12  CoreFoundation                      0x000000010ed1c1a9 __CFRunLoopRun + 905
                                  13  CoreFoundation                      0x000000010ed1bae6 CFRunLoopRunSpecific + 230
                                  14  HIToolbox                           0x00000001133a93d3 RunCurrentEventLoopInMode + 277
                                  15  HIToolbox                           0x00000001133b063d ReceiveNextEventCommon + 355
                                  16  HIToolbox                           0x00000001133b04ca BlockUntilNextEventMatchingListInMode + 62
                                  17  AppKit                              0x000000010cd233f1 _DPSNextEvent + 659
                                  18  AppKit                              0x000000010cd22cf5 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
                                  19  AppKit                              0x000000010cd1f62d -[NSApplication run] + 470
                                  20  loginwindow                         0x000000010c5b2142 loginwindow + 20802
                                  21  loginwindow                         0x000000010c5b1bf0 loginwindow + 19440
                                  22  ???                                 0x0000000000000002 0x0 + 2
    Jan 19 18:55:01 Tesseract com.apple.launchd.peruser.501[453] (com.apple.launchctl.Aqua[502]): Exited with code: 1
    Jan 19 18:55:01 Tesseract UserEventAgent[23]: CaptiveNetworkSupport:CNSServerRegisterUserAgent:187 new user agent port: 34987
    Looks like the loginwindow was crashing out.
    These are the steps I tried that didn't remedy the problem:
         repair Permissions
         repair Disk
         booted to safe mode (this caused a instant reboot at the login point)
         attempted to Log in as a different user
         repaired the volume with DiskWarrior
         reset pram/smc/smu
         emptied user and Library cache folders
         emptied /Library/Internet Plug-Ins
         emptied /Library/PreferencesPanes
    note: to make things worse the boot volume was protected by FileVault 2.
    I finally made progress when I renamed/replaced /Library/Preferences and rebooted. I could login without issue at this point.
    Turns out /Library/Preferences/loginwindow.plist had a bad value.
    Here is the contents of the "corrupted" plist that caused loginwindow to crash out. I verified this file was the culprit by placing it back in the Preferences folder. The symptom returned. I removed it once again, and was able to login fine.
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
                   <key>AutoLaunchedApplicationDictionary</key>
                   <string></string>
    </dict>
    </plist>
    and for comparison the new loginwindow.plist generated by the system:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
                   <key>AutoLaunchedApplicationDictionary</key>
                   <array/>
    </dict>
    </plist>
    As you can see, somehow a empty string was passed to AutoLaunchApplicationDictionary in stead of a closed array.
    Hopefully this post will help someone who was having the same issue I was.
    lastly, you can "kick" the login window by logging in via ssh and running:
    launchctl unload /System/Library/LaunchDaemons/com.apple.loginwindow.plist
    launchctl load /System/Library/LaunchDaemons/com.apple.loginwindow.plist

    I unfortunately can't add a solution along with my issue, but I'm hoping someone can comment.
    When I replace the contents of com.apple.loginwindow.plist with the corrected version above, stop and restart the loginwindow process with launchctl, the loginwindow launches normally and seems ready to accept a login request.
    After attempting to log in, however, the screen will flash white and return to the login window.  The contents of com.apple.loginwindow.plist then reverts to:
    bplist00?
    _OptimizerLastRunForSystem\lastUserName_OptimizerLastRunForBuild_!AutoLaunchedAp plicationDictionaryXlastUser
    Ulocalf?XloggedI/<W{?????
    ...which is odd, to say the least.  The above behavior with the white flash then comes back and the admin user cannot log in.

  • Mountain Lion login screen background, how to change it?

    I've upgraded today, and while all other customizations still work just fine with Lion Designer 3 (updated), the login background is the only one that just won't work, not even manually. I'm stuck (again, as it was after the last Lion update) with the Apple Linen image, duh. Anyone who's already figured out how to change it? I know Lion Designer will probably be updated about this, just wondering if I can avoid waiting! Thanks a lot!

    Thats what the loginox app did to me. I did not do the manual way. If needed, I dont if I can, but it might be possible for me to insert a video showing that.
    The loginox app failed to change my background.    
    applewarm wrote:
    That's what the manual way did for me too. As said in my last comment, you need to use the Loginox app instead. You can download it here: http://www.loginox.branox.com

  • Issue with Lion login screen

    Any idea why this might be happening when Lion gets woken up from sleep?

    Have you got this box ticked:
    Regards,
    Colin R.

  • Why do I suddenly have to type my password twice at mountain lion login screen?

    I am running 10.8.2 on my 2012 11" air 64GB / 4GB.
    Suddenly I have to type my password in twice when logging in. It seems to accept it, then pauses, and I have to type in again, after which it logs in fine.
    Interestingly this only happens with my main username. I have another user profile which has fewer apps and I wonder if there is some incompatibility.
    It happens both when waking from sleep & from full restart.
    I've reparied disk permissions using disk utility and onyx.
    I'm not using firevault (it is off and I believe always has been).
    I have no peripherals plugged in.
    The password thing It's a minor inconvenience only but the system has been a bit unstable recently with a occasional sudden shutdowns. Also all my chrome "favicons" disappeared after the last crash. (the double password thing was happening before this). So I wonder if there is an underlying problem
    Any ideas?

    bump

  • Lion old login screen

    Hi All,
    After drain the battery charge completely, and reset SMC and recharge the battery fully -- the login screen sometimes comes in the new version (Lion) and sometimes comes in the old version (Leopard).
    It seems that the old version comes after the screen turn off automatically or after start of screeen saver.
    Anyone know why is it happening and how to fix it to always come the Lion login screen ?
    Note: As an attempt at solution the Combo update 10.7.3 was reinstall.
    Many thanks in advance.

    This happened for the second time today. Another thing I noticed was there was no Apple chime on boot. Upon restart the machine started with the Apple chime and went into the Mavericks login screen.

  • There's a random extra line text on the login screen?!

    I would love if someone could help me figure this one out... (Just installed 10.7)
    From my first Lion log in after the update: Just above the Sleep, Restart, and Shut Down buttons on the Lion Login Screen is an extra line of text. It's definitely there on purpose (it look all pretty and formatted in a nice little band) but I have NO CLUE where it came from or where the setting/option is to change what it says!
    The text is my old company name, which changed over a year ago and all traces of it on the user profile and address book have been omitted or updated. We haven't used this name in a long time, and were very thorough in making sure all instances were updated, so that's why I'm having a hard time understanding where this buried piece of information came from and how Apple has justified grabbing it and using it on the welcome screen... What is the source of this text? I want to update it to the correct name!
    And no, it's not the computer's name, which I also thought of. That's currently set to "Mac Pro." Any ideas at all?

    Aha! Do/did you have Onyx installed?
    Onyx system utility allowed users to make a change to the file called com.apple.loginwindow.plist. It's located in Macintosh -> Library -> Preferences, and it's a locked system file.
    Onyx allowed you to edit the contents of that file and put in your own custom message. I must have done it one mine a while back (don't remember). Apparently for some people, after upgrading to Lion, the message is still there but they can't edit it anymore. The only version of Onyx that works now is the new beta version, but it still doesn't have this option.
    Anyway, here's a website with instructions on how to edit it:
    http://hints.macworld.com/article.ph...20921074429845
    I haven't tried this because my System Preferences option took care of it. Hope this helps!

  • After upgrading to Lion blue screen appears at start up have to reboot to log in

    I have been having issues when I first downloaded and installed Lion it installed then when it rebooted a blue screen would appear and nothing would happen. I rebooted the system and it came up. Now I installed the latest software update and the same thing happend did the same steps. Yesterday I had to boot my computer up twice for it to get to the lion login screen.  I have called apple and their resolution is to wipe out and restore from time machine.  Has anyone else seen this issue?

    Sounds like directory damage of some sort. A few options.
    1) Buy Diskwarrior. Probably the premier tool for directory repair. There's a download version but it needs to be run from a booted drive which it seems you don't have. You can wait for delivery of the disc which will allow you to boot from the disc and run the application.
    2) Buy an external firewire hard drive. Get one big enough for future backup use. Meanwhile, install a new version of the operating system on that drive, boot from the drive and see if you can even see the files on the main rive. If directory damage isn't too bad you may be able to copy critical ones, though the problem with directory damage is you don't know if you're copying a damaged file. That's when just getting Diskwarrior first may just make more sense.
    OSX doesn't let you make a bootable disc just by copying files onto a CD the way OS9 used to. There's a utility called CloneX that does this, but I haven't tried it. Usually what you can do is clone hte internal drive to an external drive as part of backup. The cloning places a bootable copy of the OS onto the external. Simply dragging OS files across no longer works.
    By the way, the external drive has to be Firewire in order for it to be boootable. USB is okay for backup but you can't use it to boot an older computer in an emergency (new Macs are okay).

  • Dual 2.5 G5 won't auto sleep

    Ever since I updated to 10.4.7, my dual G5 won't automatically sleep after any amount of time I set it to. The computer will sleep if I force it to either using the keyboard shortcut or through the Apple menu. The computer will also auto sleep in the other computer accounts on the same machine. For whatever reason, it will not auto sleep on my account. I few weeks ago, I created a brand new alias and moved all my files from my non-sleeping account to the new one. The auto sleep for for a few days before it stopped working.
    I've tried trashing plists, preferences, removing USB devices, stopped file sharing, and more. I changed all my settings and active programs to exactly mirror the ones on the working account - but, nothing seems to be working.
    I haven't tried flashing the PRAM yet, but I figure the problem is elsewhere since the computer will sleep on other accounts. Under my System Preferences, the extra panes I have are ATI Displays, DivX, Little Snitch, Nortorn Antivirus, Stuffit, and WMV Player. These panes also exist on the other accounts.
    Anyone have any ideas what else may be causing this problem? I'm almost positive it's software related, but I don't know how to troubleshoot further given that I've already tried to make my account mirror that of a working one.
    Thanks in advance.
    Dual 2.5 G5   Mac OS X (10.4.7)  

    Well Norton is famous for causing problems for Mac users, just search, but perhaps it could be another problem.
    Open the System Prefs>Energy Saver and set the auto-sleep to something really low.
    Now leave the pane open and unlocked and just wait for the sleep to kick in.
    Wake it up and set the time to a little bit longer, enough that you know it's not the minimum and this time close the pane.
    If this fails, offload Norton and try again.
    Norton has had a few application exploits, something to think about, also most anything from Microsoft seems to continously have security exploits.
    Also you should be cloning your boot drive occassionally, visit Carbon Copy Cloners forums for donationware software and read the "Before you clone" in their forums.

Maybe you are looking for