January 1, 0001

— type: post layout: post meta: {} title: KDE doesn’t start after upgrading to Kubuntu Gutsy 7.10 tags: - Gripes - Linux published: true status: publish — I can’t believe that the latest release of Kubuntu Gutsy (7.10) has been in beta for so long. The upgrade rendered my system all but useless because KDE wouldn’t start. When I logged in the only thing that was presented to me was the new Kubuntu background. Nothing more, nothing less. Starting Kubuntu with the Session in Failsafe mode presented a terminal window with the new Kubuntu background behind it. This was all it did, but I presume this is all that Failsafe mode does. Starting the X server using startx threw an error about the user not being authorized. I found a few links like X: user not authorized to run the X server, aborting with similar looking problems. This error was resolved using dpkg-reconfigure x11-common and changing Allowed Users to “Anybody” instead of “Console”. Running startkde then had KDE fire up but then bail back to the login screen. The last thing I saw in the terminal window was

No battery found. This is not a laptop, quitting…

This had me puzzled for a while since it looked like this might have been the problem. However, it turns out that is simply the output of the guidance-power-manager. Nothing to be concerned with it would seem, just an unfortunate piece of wording in that output. Further research suggested that deleting the ~/.kde directory may be useful. So I tried that and KDE started as before (albeit with all my settings gone) but then also quit back to the login screen. Bugger! Other vague theories suggested that reconfiguring the xorg.conf file might help. This seemed plausable since I had altered xorg.conf to support more CacheLines in the video options so MPlayer wouldn’t fall over when playing HDTV content. dpkg-reconfigure xserver-xorg was used to reset that file. Attempting to start KDE using startkde still failed. Doh! But then when I altered the Session to start using KDE instead of the Failsafe mode it all worked fine! Dammit! So, I don’t really know what resolved the problem but this was an exercise in frustration trying to find out what caused the upgrade to go so completely pear shaped. Perhaps if the Kubuntu devs had looked more closely at the KDE won’t start after upgrade from feisty to gutsy RC1 an other surprises bug I may of not had this problem.

comments powered by Disqus