The so what depends on your perspective. If you think of Linux as a hobbyist's operating system, and you get to join the party and tinker around, well, sure, th

The so what depends on your perspective. If you think of Linux as a hobbyist's operating system, and you get to join the party and tinker around, well, sure, this is just people's spare-time project, sure it's going to have bugs. I've come to the conclusion that this is the most correct view (as in, matches what the reality _is_). But don't complain about the year of Linux on the Desktop never arriving, because this kind of bug is not acceptable for a production operating system. In every commercial app I've been a part of developing, a crash is a showstopper bug--we don't ship until it is fixed. In a settings app, it's even worse, because now you've got to research how to do all this stuff on the command line. But my experience is that there is always some major bug like this with the GUI. Obviously the command line is the real interface and the GUI is just to paint the pig. Why is it never the Year of Linux on the Desktop? Because (among other things) the real interface is the command line. Ok, fine, just don't ship hobby-grade system software and expect to be taken seriously, just man up and say "the developers of this OS don't have time to write a real GUI, so it is command-line only, expect a high learning curve."