Over the last few weeks, I got a hand-me-down laptop with a dead hard drive. After replacing the faulty hardware, I thought I might try installing a Linux distro on it, just to continue my adventures with open source. Naturally, I picked the distro with the strongest reputation for user-friendliness -- Ubuntu. Now, this system certainly isn't that buff. It's a Toshiba Satellite A50 import. It's about a year old and rather slow, but did its job well enough until the choking demise of its system drive.
The last time I fiddled with Linux on my own computer was back in maybe '01, when I tried Debian on my frail old PC. That wasn't a particularly attractive experience, with some major driver issues I never worked out. Then I tried Mandrake Linux (now Mandriva Linux), which didn't work out either. The added stress of those few days seemed to have (or not) quickened my old PC's death. After that, I stayed far, far away from Linux distros, only touching RedHat and FreeBSD briefly during my brief online stints as site admins. I'm not that much of a techie, so even then, my activity was pretty much restricted to the simpler tasks.
So I grabbed the latest Ubuntu distro ("Feisty Fawn", a name I really like, too), and burnt it to a CD. Installation went straight-forward enough, until I entered a beige screen, with a white rectangular box in the top-left corner. This persisted for quite a few minutes, until the beige screen was then populated with an Ubuntu banner. Another ten minutes ticked by, and I finally saw my first message.
"There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work correctly.
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GNOME will still try to restart the Settings Daemon next time you log in."
The system stopped reacting after then.
Googling GNOME Settings Daemon Ubuntu startup error proved fruitful, though perhaps not so helpful to myself, with my limited Linux expertise. There was a variety of advice, but nothing definite or particularly relevant came to me. A little frustrated, I checked the disc for errors (none, as the built-in tool indicated) and went for Kubuntu (opting also for Feisty Fawn, if just for the name). Perhaps KDesktop would work better if GNOME decided to act up on me.
The installation certainly went a bit smoother, and I liked the colour scheme better. But something similar happened.
KDesktop said, "The process for the file protocol died unexpectedly."
Again, the system hung. At least I got to see part of the GUI. Yay.
Hmm... Kubuntu KDesktop dead upon installation? I decided enough was enough, and dug out my XP CDs to see if the hardware was truly messed up. And the system booted up fine. Ugh.
Maybe if I feel more adventurous another day, I'll give it another shot. Maybe Gutsy Gibbon'll fix the mysterious issue for me. Maybe I just have a Linux/Ubuntu-hating machine. I suspect the last is probably the most probable explanation...