My Downgrade to Hardy

I upgraded to Kubuntu 8.10 a week after release of the new Kubuntu. Just like most other Ubuntu flavored Linux users. I was excited. I like what Canonical is doing. When Intrepid released, I heard many good things about the new revamped KDE 4.1. Many of the original 4.0 eye sores and reliability issues were supposedly solved, so I prepared myself for the upgrade.

The time was here to upgrade now. I decided to use the CD upgrade method. From the Konsole, a couple of easy commands started the process. After the update process finished, I immediately booted into KDE4, obviously. I was impressed by how it looked, and I immediately started tinkering. I added a simple clock to my desktop… crash. OK, I was shown a fresh new desktop, just like it came out-of-the-box. I added my most common shortcuts to the kicker bar… crash. Again, new out-of-the-box desktop. Hmm. What is going on. I logged out of X completely, and exited to a console login screen. After I logged back in, i “cd” to my /home/chris/ folder and deleted the .kde and .kde4 folders using rm -r, thinking this should have wiped any previous KDE 3.5 settings. Wrong. Crash after crash still happened.

I have given Kubuntu a solid two weeks of everyday use. I finally gave up. I could not stand the instability any longer.

As of November eighteenth, I downgraded back to Hardy Heron LTS. I plan to use it till the new version of Debian releases, Debian Lenny. I am in desperate want/need of a solid and stable Debian, or Debian based Linux release. Kubuntu Hardy Heron just happens to be the one for now.

Tagged with:
 

2 Responses to “My Downgrade to Hardy”

  1. ewr2san says:

    Im in the same boat. After struggling with a too many video issues with no fix, I just cant handle the instability of KDE4 on Intrepid. Back to Hardy for me. Feisty, Gutsy, and Hardy were rock solid Kubuntu releases, Intrepid is just too unstable. Too many crashes on my hardware. What did work was pretty, and speed was acceptable, but without stability it just isnt a go.

  2. [...] wanted to give KDE4 another try. I tried it about a month ago and did a post about it here. After listening to many podcast with the lead developer of the KDE4 project, Aaron Seigo, I really [...]



Bad Behavior has blocked 269 access attempts in the last 7 days.