Apple OS X 10.5.6 Update Breaks Some MacBook Pros

Newscloud writes "As PC Mag reported last week, Apple OS X 10.5.6 can break some MacBook Pros leaving some users (like me) with a dead backlit black screen after the Apple logo appears. While I initially thought I had a hardware failure, it turns out that there is a fix as long as you have an external display, keyboard and mouse. The problem only appears on the second restart, so if you sleep your MacBook a lot as I do, you might not realize the problem is related to the OS update you did the week before. The problem was related to older, incompatible firmware that Software Update wasn't flagging before the upgrade. This definitely gives weight to the argument for waiting a bit to run software upgrades."

Comments

News! OS X update breaks MBPs and /. decorum!

[earlymon]

No, I'm not new here.

Neither am I trolling, neither is this flamebait.

It's just that there a LOT of posts complaining that if this were to happen with an MS update, the Apple gang would be crucifying them and a lot of negativity that this is funny.

Mismanaged updates by either corporation - Apple or MS - is indefensible and inexcusable, and it's usually a real problem for the victims.

The occasional screwed-up update from Apple is something Apple users are - unfortunately - used to experiencing. Ditto for the MS users. Given that I'm a user of both, that's just my experience.

I think we excuse Linux problems (I'm a user of that, too) because the software was free. There's some merit to that, but as I think about that statement it does make me ponder... In any case, the real demerits of the OS choices are overlooked at times like this:

1. Linux not liked because no corporation stands behind the OS potentially misbehaving. This is a real problem in the minds of many corporate managers who have to oversee risk.

2. OS X is the "odd man out" where corp mgrs don't want that risk.

3. MS may obsolesce something that worked for the whole organization in favor of something that seems to work less well, another risk issue for corp mgrs.

The fact that an update involving any of the three might screw something up is neither a decision-point nor cause for immature glee.

The problem from TFA is an unfortunate and foreseeable consequence of testing getting the short-shrift.