Previous 1 2 3 4 Next 267 Replies Latest reply: Nov 17, 2014 10:33 PM by flipperfeet Go to original post Branched to a new discussion.
  • SirHomeALot Level 1 Level 1

    Sam problem with 2011 iMac 2.7Ghz Core i5, since updating to 10.8.2 - didn't happen immediately though.

    Anyone try rolling back to 10.8.1 to see if that fixes it?

  • JohnnyGTO Level 1 Level 1

    Early 2009 with 10.8.2 same problem.


    I am able to ssh in from another competer and "sudo shutdown -h now" (-r for reboot does not work) successfully. I rather force the computer to shut itself down properly then use the power button and chance corupting anything.

  • James2509 Level 1 Level 1

    Exactly same problem om my Macbook Air 11 inch Mid 2011. Upgraded to 10.8.2 a couple of days ago but problem only started yesterday. Has happened about 2 times, where just refuse to wake up from sleep. Interestingly when looking at Console Logs, on both occassions the last entry in the log is as follows:


    Signal[274]: Error Code=-3930 "Operation not permitted" UserInfo=0x400389500 {NSLocalizedDescription=Operation not permitted}


    No idea what this means. Anyone know.


    At moment, as Macbook Air is plugged into Monitor and in clamshell mode, is to set it to never go to sleep in the power preferences.


    In General I have found 10.8.2 to be very buggy, have also had problems with Key Chain and ubd process creating 1000s of certificates and slowing everything down. Seriously considering rolling back 10.8.1.


    At moment feel like I am living in Windows Vista World

  • maccampb Level 1 Level 1

    I'm seeing the same thing on my MBP mid 2009 Core Duo, 3.06GHz. I'm making sure I save everything everytime I put it to sleep until Apple fixes this...

  • stoopkidsgonnaleave Level 1 Level 1

    I'd be curious to see, does this occur with all types of sleep occurrences?


    Macs will go to sleep 1 of 3 ways:

    1. Software timeout sleep

    2. Clicking  > Sleep

    3. Hardware mechanisms: On portables closing the lid activates a magnetic sleep switch, on desktops quickly pressing the power button sends it to sleep.



    Anyone willing to post a copy of their logs from after attempting to sleep? If so:

    1. Mark the time you put the system to sleep

    2. After a reboot open Applications > Utilities > Console

    3. Under kernel.log, provide the logs from the time your system went to sleep, till whatever the current time is.


    Might be interesting to see if there's some weird issue causing the systems not to enter sleep correctly.

  • jadewocky Level 1 Level 1

    I've seen the same problem twice so far since upgrading to 10.8.2 on my MacBook Pro late 2008.  When trying to wake, just get black screen.  Nothing works, except powering off.


    I don't know if the computer was actually running or not, since that laptop had all sharing turned off.  SInce it happened a second time, I've turned on remote login and screen sharing.


    Just saw a twist on what others have been reporting.  Went to wake it just now.  It is showing the login screen, but is not responding to any user input, and the password field is not highlighted.  This may be the same problem, just happening slightly later in the wake up process.


    However, I'm able to verify that the machine is actually running, since I just did a remote login (oddly it's not showing up for file sharing on my network).


    I'm looking thru the system logs now... but not seeing anything that stands out as an obvious error related to sleep/wake.  Any suggestions for what to look for?

  • jadewocky Level 1 Level 1

    Weirder yet... went to shut the machine down remotely via "/sbin/shutdown -h now" and it has so far not actually powered off (after 5 mins).  It killed all the services, so I can no longer remotely log-in, but the computer is still powered up with the login screen displaying (although again, doesn't respond to any user input).  I've never had that happen before...

  • Luki86 Level 1 Level 1

    Same problem with my MacBook Pro Retina.

    Apple, please fix it asap.

  • PauloAF Level 1 Level 1
  • jobeau Level 1 Level 1

    I erased my hard drive and did a clean install of OS X and it looks it solved the problem for me. I'm using a MacBook Pro (mid 2012, non-retina).

  • KarlW Level 1 Level 1

    Is there any way to do a clean install without wiping out your whole hard drive(seems excessive to me)? Like the old archive and install in 10.2, much more civilised. Thanks.

  • SASanderson Level 1 Level 1

    I believe that the Take Control of Upgrading to Mountain Lion ebook from Tidbits discusses how to do a clean install that is the equivalent of the old archive and install. Catalog | Take Control


    I wasn't anticipating having to do this so haven't yet read the clean install chapter.

  • KarlW Level 1 Level 1

    Hah! I was literally just looking at Joe Kissell's Upgrading to Mountain Lion ebook at Take Control and wondering if to get it. I will now do that. Thanks SASanderson.

  • Mattowski Level 1 Level 1

    This is the same problem for me. Though only on 1 of the 2 computers. The MacBook Pro i7 Early 2010 is fine. My work Mac Pro 2.66Ghz Quad-Core Intel Xeon will not wake from sleep. It used to on 10.8.1


    My only option is to turn off the computer. Not ideal. I wonder if actually the problem is the screen sleep not the machine itself ?? Just an idea.


    This is a problem I used to have in one of the versions of Lion too. I suspect its something thats crept back in again.


    Bloody annoying though. I don't wish to shut-down my work machine each night in case I need remote access.


    Checking the console it would appear there is rather a lot of activity overnight with the following entry starting the activity...


    24/09/2012 20:14:45.000 kernel[0]: Wake reason: RTC (Alarm)

    followed by...

    24/09/2012 20:14:45.000 kernel[0]: RTC: Maintenance 2012/9/24 19:14:44, sleep 2012/9/24 17:14:46

  • ErwinLiemburg Level 1 Level 1

    I had the same issue with my early 2009 MBP. I found this option to reset the SMC, it fixed my wake-up problem. Check how to reset the SMC here:

Previous 1 2 3 4 Next