You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

OS X Lion 10.7 Sleep Issue

Installed Lion this morning and the only issue that I have found thus far is sleep.


I use an external display as well as the laptop display. When I close my MacBook lid and wait several minutes, I do not get the sleep mode winking LED and my second display does not go into standby, probably because the Mac has not entered sleep mode.


When I raise the lid, my laptop display appears to have been in standby and the Mac looks to be doing a device discovery. After the discovery, the Mac display is normal but all the apps from my second display are now on the Mac display.


Anybody have a clue as to the cause or is Lion just broke?


Cheers

MacBook Pro, Mac OS X (10.7)

Posted on Jul 20, 2011 1:44 PM

Reply
251 replies

Aug 27, 2011 2:35 PM in response to Tevis Money

Thanks for the link, but it is not relevant for my situation: my MBP refuses to sleep when the lid is closed, even if the secondary screen is switched off. The KB mentions that the screen must be switched on for clamshell mode. I really don't see why a machine should stay awake when the lid is closed and the secondary screen is switched off.


Also, until Lion, this has worked as I expected: the machine sleeps when the lid is closed and the secondary monitor is switched off...

Aug 29, 2011 5:32 AM in response to jcarpio

Worked for me - was driving me a bit insane after the Lion upgrade ...


Active Profiles:

AC Power -1*

Currently in use:

hibernatemode 0

disksleep 10

womp 0

networkoversleep 0

sleep 0

powerbutton 1

ttyskeepawake 1

hibernatefile /var/vm/sleepimage

autorestart 0

panicrestart 157680000

displaysleep 30


Culprit in my case was:


0 82 1 0 7:35pm ?? 0:00.06 /usr/libexec/InternetSharing


Switched it off in preferences - thanks!


Message was edited by: Perapoika (Oops, screen capture was AFTER I switched Internet Sharing off ... it did say sleep was being prevented by PID 82)

Aug 30, 2011 4:41 AM in response to ApexRon

I had this problem but I managed to solve it and have my MBP sleeping again.


I tried resetting both SMC and PRAM but it did not work. Even if I had almost every "sharing" unchecked (System Preferences -> Sharing), I checked every "sharing" box (except XGrid), and then unchecked the sharing I was not interested in.


Now it works again. So:

1. Go to System Prefences, Sharing

2. Check every box;

3. Uncheck the boxes you are not interested in.

4. Apple -> Sleep: it should work.


Congratulations to Apple for this weird bug.

Sep 5, 2011 8:06 AM in response to ApexRon

I apologize if this has already been mentioned ... I did not read all 9 pages of the thread. I solved my sleep issue by using the command


pmset -g assertions


to see which process had set PreventSystemSleep. In my case, I saw


Listed by owning process:

pid 20: [0x0000012c00000014] PreventSystemSleep named: "org.cups.cupsd"


This is the print driver. Sure enough, it thought that it was printing something. As soon as I deleted the item that it thought that it was printing, the problem went away. I could have also fixed it by actually printing the item, but it was there because I forgot to hit the PDF option and inadvertandtly queued an item for the real printer.

Sep 6, 2011 9:15 AM in response to ApexRon

MNSteve... Good tip but I did not have any processes that would prevent sleep


AllenW in SF... I tried ALL sharing method you described and still no fix.


I agree that with having a second display it would be nice if I closed the lid on my MBP the second display would become the primary display. However, not having an external keyboard makes it difficult to use.


I still believe that Apple FUBAR'd the lion code by not giving me the option on what to do when the lid is closed.

Sep 6, 2011 11:35 AM in response to AllenW in SF

I think that there are a couple of morals to the story of a 9-page thread on sleep problems in Lion.


One of them is that sleep is complicated, and there are many reasons why the system might not sleep. This is touched on in a support article in the support website, but it's woefully incomplete. I suspect that many of the sleep issues may not have anything to do with Lion, just as mine had nothing to do with Lion.


As for problems in Lion . . . I'm in no position to speculate about whether it's "worse" than any other release. Yes, there are lots of posts here in the forum, on various topics. But look at the number of people who have upgraded to Lion. Is the traffic here any heavier than it has been for previous upgrades? I don't know; just exploring the issue. It would be interesting to see some actual statistics about how many people had problems related to their upgrade to Lion, compared with previous releases. I don't expect to ever see anything that objective.


Any new release of anything is guaranteed to cause problems for a subset of the peole who install it. Personally, I continue to suffer from a problem that my wireless connection doesn't restore after a wake from sleep, a problem that was introduced in a previous upgrade, fixed in that upgrade, then regressed with Lion. It ittitates me. But I'm not ready to write off Apple just yet.

Sep 6, 2011 2:07 PM in response to ApexRon

MNSteve,


I don't believe sleep is complicated. However, the rules as to when sleep should occur or be permitted need to be reviewed by Apple development because for lion the rules are incomplete or just not working. In addition, should there be a process that is preventing sleep, it would be nice to know about without having to bring up the terminal app and key in some obscure command.


All and all, I believe that Lion is fantastic, though I admit there is some work to be completed in certain areas. Granted, I had to learn some new trackpad motions but oh well I am over it.


Due to work requirements, I had Windoze for many years. Believe me, I am not going back.

Sep 7, 2011 2:41 PM in response to jcarpio

jcarpio wrote:


SOLVED:


if your mac is not sleeping properly (mine was not sleeping only when the power was plugged in) do this:


open terminal:

run pmset -g (you'll get an output similar to this)

Active Profiles:

Battery Power -1

AC Power -1*

Currently in use:

womp 0

autorestart 0

halfdim 1

sms 1

panicrestart 157680000

hibernatefile /var/vm/sleepimage

networkoversleep 0

disksleep 10

sleep 0 (imposed by 18)

hibernatemode 3

ttyskeepawake 1

displaysleep 10

acwake 0

lidwake 1


see the line "sleep 0 (imposed by 18)"? that means pid 18 is forcing sleep to be disabled, that's what the zero 0 means.


now do "ps -ef |grep -e 18" and find out what 18 is. mine was cupsd or internet printing. in preferences, print and scan, i unchecked, share this printer on the network.


i re-ran pmset -g and got:


Active Profiles:

Battery Power -1

AC Power -1*

Currently in use:

womp 0

autorestart 0

halfdim 1

sms 1

panicrestart 157680000

hibernatefile /var/vm/sleepimage

networkoversleep 0

disksleep 10

sleep 10

hibernatemode 3

ttyskeepawake 1

displaysleep 10

acwake 0

lidwake 1


put the mac to sleep and it worked just as expected!


Solved it for me. The sleep was prevented by an accidental print to a disconnected printer.


Anton-Junlens-MacBook-Pro:~ antonjunlen$ pmset -g

Active Profiles:

Battery Power 1

AC Power -1*

Currently in use:

standbydelay 4200

standby 0

womp 1

halfdim 1

panicrestart 157680000

gpuswitch 2

hibernatefile /var/vm/sleepimage

sms 1

networkoversleep 0

disksleep 10

sleep 0 (imposed by 30)

hibernatemode 3

ttyskeepawake 1

displaysleep 10

acwake 0

lidwake 1


26 99 30 0 7:27PM ?? 0:00.51 HP_LaserJet_Professional_P1102 ...... bla bla bla....


removed the document from the print queue and ... the computer took a nap.

OS X Lion 10.7 Sleep Issue

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.