If you have upgraded to Mac OS X 10.5.2 and use a MacBook Pro with an external display in closed-lid mode, do not install Leopard Graphics Update 1.0. Once Leopard Graphics Update 1.0 is applied, your MacBook Pro will mistake the external display for a second internal display and it will not function in closed-lid mode.
This appears to be a widespread issue. An official bug report has been filed and Apple may be addressing it soon. For now, you can force your MacBook Pro to use the external display by closing the lid immediately after pressing the power button, before the chime.
Update: This issue has been corrected by the release of Mac OS X 10.5.3.
Thanks for this James.
I’ve been working in clamshell mode for some time now, even after updating to 10.5.2 w/ graphics update. I read your article over the weekend and thought “I’m lucky, I guess”, then came to work today to do my normal hook up to sleeping MBP, and… nothing but what you’ve outlined above.
You’ve saved me a ton of troubleshooting today. Using your startup tip, I’m able to at least get to work. I filed an Apple Bug on this. I’m sure they’ve gotten a ton already, but one more might help get a fix out the door.
You’re welcome! I’m glad that I could spare you the headache of troubleshooting this (I spent about 2 hours on it before finding that thread on the discussion forums), and I hope Apple addresses it soon.
[…] it was the external monitor debacle that bit me, now this! Has anyone else had this happen to them? How did you deal with it? Is there […]
Like I said – I filed a bug on it w/ Apple this morning. They responded this afternoon that it’s a known issue – so it’s somewhere in the fix queue. I hope it’s near the top.
Well, at least they acknowledge it as a known issue, and it shouldn’t take long for them to release a fix. Until then, I’m enjoying how much time I’m saving without having to sleep/wake the computer to use the external display.
Thanks. I was bitten by this yesterday and your tip helped me work-around.
You’re welcome! I’m glad that it worked for you, but you may want to consider updating to the latest release of Mac OS X 10.5 (currently 10.5.4) as soon as possible. It fixes this issue and several others.