Submitted for your consideration:
I’m not trying to start a flamewar; I just thought the irony was amusing. Obviously any complicated software like an operating system can have problems, but I’m sure someone at Apple right now is sighing and thinking, “Why did it have to be blue?”
The way I heard it, it all used to be the Black Screen of Death once. Blue’s just a nicer colour while you’re grieving over hours of lost work.
Yes, I was surprised to read this as well. I had no problems installing it.
I’ve installed it on 8 machines so far and it’s all gone smooth as silk.
I did notice after installation, the first reboot takes a lot longer than normal, and is on a plain blue screen this whole time (with it toggling between arrow and beachball every so often). I wonder if some machines are getting stuck in this mode.
FWIW, Leopard is the best OSX update yet, IMHO.
People have been warned by Apple before that some third-party hacks that diddle with low-level system resources will more than likely cause problems eventually. Unsanity has acknowledged the issue and give advice for a workaround.
An Archive and Install option, as posted here, is usually recommended for any upgrade install, particularly if you’ve been screwing around with your system. That solves this particular problem too. If people hadn’t installed the haxie framework (which has had some documented incompatibilities in the past, including full-on kernel panics) and hadn’t taken the least conservative upgrade path they wouldn’t have had this problem in the first place. There’s a reason Apple put “enhancement” in quotes. They’ve gotten flack in the past when Unsanity’s software caused trouble, which is annoying considering they’re getting blamed for a third party’s mistakes.
I’m of the opinion that if you do something — not supported by the OS maker — that has the possibility of undermining the stability of your system, and the system crashes or has some other problem, it’s completely your fault. That’s especially true in this case, where Unsanity has a bad track-record. Besides, only some wacky fringe folks will claim that OS X is perfect. It’s not; it’s just a buttload better than the alternatives. Contrast that with Windows installs where it sometimes crashes on a new or nuked disk, and you’ll see why the irony isn’t all that biting.
Apparently, there’s an “easter egg” in Leopard, where if you have an AirPort router you can navigate your way to the image of a PC showing the BSoD.
I was just all-but forced to upgrade from 10.4.something to 10.4.10 (iTunes all-but forced an upgrade which required the OS upgrade). The first startup after the install always takes forever. I was on the faux-BSoD for like 30 minutes.
My friend told me this weekend that VMware virtual machines give the purple screen of death. 
From what I’ve read, most of the reported occurences have been attributed to Unsanity software installed unbeknownst to the user as a part of Logitec Control Center, whatever that is; all I know is it doesn’t appear to have been included with the drivers for my Harmony Remote 880.
I just read about that this morning. More detailed information at Daring Fireball. The Logitech Control Center is software that manages the button mapping and extended capabilities for their keyboards and mice. According to the DF link, backed up with cites from Apple, developers are strongly warned not to put stuff in the /System/ directory, but the makers of APE did it anyway.
The blue screen problem apparently comes from the installer faithfully copying over everything that’s in the /System/, assuming that if it’s there that it’s essential system software put there only by Apple. The older versions of APE aren’t compatible with Leopard, so it screws things up on boot.
The guy at DF is right, that link on the Apple Support page looks like it was written by someone who was pretty pissed at Unsanity and other third-party people who can write software but apparently can’t follow simple directions.
I got this blue screen of death when upgrading. Freaked me out like cause i didn’t backup (isn’t that what time machine is for). But the instructions floating around the web fixed it like a charm.
Still given the prevalence of this bug, Apple should have done more real-world testing to catch this issue before Leopard’s release.
I didn’t upgrade. Well, I did, but I wiped the hard drive first. Had a couple reasons to do it, but I’m sure some of it is force of habit from the way I deal with Windows.