Bullet Proofing OS Components

So, Ubuntu wanted a "bullet proof X"...however there are other essential components which will essentially kill ANY chance of adoption by 1st time user. For example, HAL. I'm currently have issues with HAL and can't utilize wireless (and probably USB). I can connect to the internet but cannot initialize FireStarter because it says the device eth1 isn't ready.

This is just given as an example. The point is, Ubuntu is too buggy for serious consideration. I'd never think anything like this would happen in Windows or OSX. I propose that the different Ubuntu components be reviewed and that guidelines, specs, and features be drawn-up with the intent to make many more "bullet proof" system components. For instance, it seems each release kills OOo for some people...then the forum "help" gets many people saying "uninstall this or that package", and "re-install", and "do this or that...". This isn't "help" and may harm the system further. We need more than guesswork, the system itself needs to diagnose and tell the problem in an understandable way: stupid hacks which work are still dangerous and faulty. Some of the OOo "fixes" are due only because there are themes incompatible with OOo gtk. Change the theme and it works: however the users shouldn't have to do this if the features available are what they're using...why does GTK conflict in the first place? Why aren't there safety features built-in? On my system all I had to do was delete the OOo conf/home/whatever files and upon re-start of the program it wrote a new one and voila! it worked...but why did I have to?

Time to make a bullet-proof OS. : )