iMac with Lion not waking after overnight sleep

Update: no luck, the problem come back. Now, try to disconnect trackpad, but I don't think it is the trackpad. As the other mentioned, it is bluetooth problem. Let see this time.

You're right, Simon. The problem is not related to the Trackpad as so many have suggested. This issue affects machines without Trackpads as well as those with them.

I turned off my trackpad and it resolved the problem for a while. Yesterday, my imac did not wake up from sleep. There was not trackpad connected. Unfortunately I need to report that the trackpad alone is not the problem. There is something wrong with the bluetooth in Lion. The update did not resolve the problem. I have a macbook air with an upgrade to Lion that does not have this problem.

I have just had this a couple of times in the last few days on an MBP. Bluetooth is off. Here is an extract from the Console System Log. It looks like it is an error with the screenlock authentication.

I shall send a bug report to Apple.

Note that they do not read these user forums, and the way to report is via their form:

https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/wa/signIn

System Log Extract:

23/10/2011 01:55:34.653 xpchelper: for uid: 504 -- timeout while waiting on FSEvents flush; clearing cache.

23/10/2011 01:55:41.353 loginwindow: ERROR | -[LWBuiltInScreenLockAuthLion _handleAction:forController:] | Unknow action received, LUIBackgroundPressed

23/10/2011 01:55:47.332 loginwindow: ERROR | -[LWBuiltInScreenLockAuthLion _handleAction:forController:] | Unknow action received, LUIBackgroundPressed

23/10/2011 01:55:47.604 loginwindow: ERROR | -[LWBuiltInScreenLockAuthLion _handleAction:forController:] | Unknow action received, LUIBackgroundPressed

23/10/2011 01:56:45.000 bootlog: BOOT_TIME 1319331405 0

Hello Putnik,

in the MBP unibody there is a magnet in the closing lid: "faulty" or "unaligned" magnet has been the cause of sleep/wake problems sometimes.

Strange as it may be, I concur that sometimes it seems to depend on how "cleanly" you open the lid. Maybe this [LWBuiltInScreenLockAuthLion _handleAction:forController:] error is caused by multiple inputs from the switch. I've seen this on most computers I have owned.

I have a similar problem on my dual quad core Intel which I foolishly upgraded to lion as a matter of fact I have 2 separate issues affecting the machine waking up from sleep.

sometimes I just can't log back in no matter whether I use the space bar or any other key or the mouse the password window will not appear and I have to force shut down the machine.

but recently what also started happening is that the password window comes up but then the whole screen turns grey and it seems like the machine restarts itself but without the welcome chime. it then takes around a minute until all software is opened again.

I do not have a single machine, and I've got 6 of them, where lion is running without problems I converted this machine back to snow leopard and everything is working flawlessly again.

unfortunately my new iMacs I cannot downgrade.

I just brought my imac to service center to be repaired(late 2009 27" intel core 2 duo) I was having same sleep issues with sleep . They think it may be a bad logic board. I was reading the post on this topic and saw what you had written . I do not understand where you change those settings. It was where you listed 0,1,3,5,and 7

Well... as for logic board being bad, you might want to rethink that, we did not have this problem before upgrading to lion, and as for the service centre saying it's a bad logic board, lets me know just how much training they have.

I talked with them yesterday and they said were not able to duplicate problem. suggested I bring in my devices BT etc that I use , to see if that would make it fail so they could identify and fix. This is getting old quick.

I was having this problem until I unpaired my track pad. Has worked fine since. I even re-paired my track pad hoping that it was my imagination and it started again! As soon as unpaired it all was fine again. I'd look at your BT devices.

Similar issues with late 2009 27 inch iMac.

I am currently using an apple bluetooth keyboard and apple magic trackpad but also have some older bluetooth devices listed in the bluetooth settings that I don't use anymore. The non-wake issue has become worse in the last week to the point that it will happen every time if I leave the computer for thirty minutes or more. I'm on the latest iteration of Lion (upgrade from Snow Leopard).

Having read the whole thread, I'm going to try the following:

1. Shutdown and repair disk permissions

2. Delete all bluetooth devices then re-pair first with keyboard and second the trackpad

3. Change my power settings to sleep the whole computer after 30 mins (currently only sleep monitor)

4. Move my powered usb hub to usb slot number two

And of course, cross my fingers until Apple releases a proper fix !

Hi all,

I had separately posted this problem at https://discussions.apple.com/thread/3471686?answerId=16653952022#16653952022 before finding this thread. Perhaps my post adds something to the discussion as I have related this whole problem to USB!!

"

I have an iMac 2009 and since having upgraded to lion my Bluetooth devices (keyboard, mouse and pad) hang after a few hours in sleep mode. I am pretty sure this only happens when USB devices are connected.

If I disconnect all of the USB devices, the MAC is OK for days (perhaps forever). If I attach any USB device and leave the MAC sleeping overnight the bluetooth devices are invariably hung in the morning. I have tried adding the devices individually (USB Hub, APC UPS, PayPen USB Hub, iPhone, iPad) to try and find the culprit, but it appears that any of these can cause the problem even the Hub alone or just an iPhone.

Some seem to be worse than others in causing the hang (PayPen seems to be the worst) but I cannot be certain of that. At the moment I have unplug all the USB devices whenever I leave the MAC alone.

"

I got a reply Barry Hemphil who suggested:

"I have not seen a similar problem...

However, try a couple of things:

Trash a preference file (com.apple.bluetooth.plist) and restart.

Reset the PRAM

Reset the SMC.

As an aside, Bluetooth does use USB hardware in some fashion, so there could be some correlation.

Barry

"

But none of that helped.

Does this USB connection help any of the Tech gurus to figure this one out??

Thanks

igs

I resolved this problem by connecting Apple USB keyboard to iMac. When my mouse and trackpad do not respond, but the direct connected keyboard always wake my iMac up. Once the machine is up, the mouse and trackpad begin to work. I have this setup for 3 weeks now, and wake up the machine everytime.

Beside, I like the full side keyboard, so I am happy with this setup.

I submitted a bug report to de Apple Developer Bug Reporting Team:

When my iMac (21,5 inch, late 2009) is sleeping for a longer time (overnight) it is not possible to wake it up using my bluetooth keyboard, magic mouse or trackpad. The only way to wake it up is pressing the power button. But then my keyboard, mouse and trackpad all appear to bedisconnected. The only solution it to perform a hard reset/reboot.

I already took the following steps, all without result:

- Resetting my Mac's PRAM and NVRAM (http://support.apple.com/kb/HT1379?viewlocale=en_en)

- Resetting the System Management Controller (http://support.apple.com/kb/ht3964?viewlocale=en_en)

- Emptying all the caches.

The only work-arounds that really work are:

- Disconnect my trackpad

- Setting the hibernation mode to 0 or 1

But these are work-arounds and no serious solutions!

This is what they replied:

###

This is a follow up to Bug ID# 10332258. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 8360414. The original bug number being used to track this duplicate issue can be found in the Related Problem section of your bug report's Problem Detail view.

###

So the good news is that Apple knows about the problem. The bad news is that they do not seem to have a solution yet.