This is a new feature in lion. It happens when you have an external display hooked up to your macbook and switched on and the mag safe is connected. I like this because I can now connect it to and hide it behind my TV when I'm at home and control it with the bluetooth keyboard and magic trackpad from the couch across the room.
If you need it to go to sleep mode, just turn off the external display while the lid is closed or unplug the mag safe.
Message was edited by: buttonbag
Thanks Markosys, pmset -g worked for me. I realised that my problem was created by "boom" an audio booster.
Because when my mbp 13" goes in sleep, when I get back from sleep, the audio does not work, like boom frozen, I have to ALT-CLICK on the audio icone and click headset.
When I did pmset -g I saw that my displaysleep was imposed by pid 141, which was /usr/sbin/coreaudiod , by ALT-Clicking the imposing disapeared and sleep worked again.
Here we go
I now have OS 10.8.2 and the same problem exists as in the prior release.
However, my issue is not caused by a defect but by an oversight in Apple's usability requirements for OS.
I have an external display for my MacBook Pro that is used as a second (not mirror) display. The Apple requirements assume that if I have a second (not mirror) display I must also have an external keyboard. Therefore, when I close the MacBook Pro I must want to use the second (not mirror) display as a primary with my external (non-existent in my case) keyboard. Consequently the MacBook Pro does not sleep unless I use the OS pulldown or keyboard keys to force it.
Had the Apple requirements people the proper foresight they would written the requirements such that an option would be added to System Preferences that if I checked a box, the MacBook Pro would go to sleep when the lid was closed.
Using pmset -g worked for me, but
If you prefer to NOT use the terminal, for "pmset -g" this fellow has created a simple graphical program that tells you the name of any process preventing your mac from sleeping.
Breaking News I found a Solution!
I have a Mac Pro 1,1 that does not have a wifi card nor Bluetooth. The issue I am having is loosing my Internet connection after waking from sleep. My network preferences indicated the ethernet cable was unplugged when I know that wasn't really the issue. I was convinced this had to do with Lion because it didn't occur in the previous operating system.
Here is what I did to prove my case.
- 1) I installed a new disk image of Lion and checked if the Internet would drop after sleep. Sure enough it did.
- I plugged my Internet connection directly to the computer instead of going through my router. That didn't stop the issue.
- I did every recommendation on the Internet I could find. That was unsuccessful.
- I downgraded to the original 10.4.7 on another internal hard drive that was being used. During the install I received an error and operating system failed to install.
- After researching on the WWW, a Mac user mentioned that you should unplug your "FireWire drives" before installing. Sure enough, the install completed succesfully after removing my WD FireWire external hard drive. Just as I suspected there were no issues with the Internet dropping after waking from sleep, it worked perfectly!
So is Lion to Blame?
Just as I was getting ready to officially point the finger at Lion, I decided to run one more test.
- Start up Lion without my FireWire hard drive connected.
- Put the computer to sleep and check to see if the Internet will drop anytime with the next 24 hrs.
- Cant' believe the Internet never lost it's connection. I CANT BELIEVE DISCONNECTING MY FIREWIRE DRIVE FIXED THE INTERNET ISSUE DROPPING UPON WAKING FROM SLEEP!
- Celebrate like a hero, the problem is gone.
In my opinion this issue is probably still related to Lion since it seemed to pop up on the radar just after I upgraded to this operating system. My theory is perhaps communication to my FireWire hard drive is delaying the wake from sleep function and as a result causes the handshaking opportunity to regain the tcp/ip connection to fail. Sort of like missing the bus!
P.S. I hope someone who is more technical wouldn't mind looking into this further. Perhaps understanding why my FireWire drive causes the Ethernet connection to drop will shed light on this long lasting plague. I'm also curious how I can fix this issue so I can keep my hard drive plugged in. Thanks for any help.