Screen After Sleep Mode

Discussion in 'Mac Basics and Help' started by Flyer77, Mar 25, 2008.

  1. Flyer77 macrumors newbie

    Joined:
    Jun 5, 2007
    #1
    Does anyone experience their screen not turning back on after your computer leaves sleep mode, such as the screen just being completely black and the only way to get the screen working is to restart the computer? I'm experiencing this about once a week or so now.
     
  2. b1u3b0y Guest

    Joined:
    Mar 24, 2008
    #2
    If you're using Leopard supposedly it's a glitch with the update.. many people have been talking about this. I'd use the search and see if any other threads have come up with a solution.
     
  3. kingpikey macrumors member

    Joined:
    Jun 25, 2007
    #3
    Something I've noticed...

    If I leave my logitech wireless mouse receiver plugged in when closing the lid to my MBP, when opening the lid to wake the computer up, striking keys or using the touchpad won't bring out out of sleep... but moving my external / usb / wireless mouse does.

    Haven't really tested it, but it's seemed to work the last 2 times for me.

    Hope this helps.
     
  4. ncavs10 macrumors member

    Joined:
    Mar 17, 2008
    Location:
    CT
    #4
    mr. feeny has a thread about that. he has a macbook pro and experiences this on a regular basis. he spoke with apple and they said that it is a glitch in the software that they have gotten many complaints about and that they claim to be working on a fix for it in the next software update. i have a macbook and have not experienced any issues and neither has my roommate. it could be a macbook pro thing...i dont know what youre using though.

    also, he noticed that if youre using the istat pro widget, it worsens the situation, so removing that widget from your dashboard and deleting it completely made it slightly better.

    best of luck.
     
  5. flopticalcube macrumors G4

    flopticalcube

    Joined:
    Sep 7, 2006
    Location:
    In the velcro closure of America's Hat
    #5
    I have experienced that on my MacBook. Usually putting the machine back to sleep and waking it up again solves the problem for me.
     

Share This Page