After having loaded the KDE desktop with the help of the failsafe
console (and then starting kwin, kinit, kdesktop, kicker manually),
reconfiguring the KMenu, adding a new applet (Kima) to the kicker and
logging out from this session I was now able to normally login to KDE as
if there never was a
Public bug reported:
Today I tried to upgrade my installation from Feisty to the new Gutsy
RC1. For Upgrading I used aptitude. The new packages seemed to install
properly so I rebooted after aptitude finished upgrading.
After the reboot I tried to login to a KDE session from kdm, which left
me
I can also confirm this bug with 2.6.22-14-generic on Intel Core Duo
with ATI Mobility Radeon X1400.
ps shows running getty instances but switching to tty1-6 shows a blank
screen with a white blinking text cursor.
--
tty[1-6] are active but display nothing in Gutsy
I just saw that the problem with the blank tty1-6 was already mentioned
in bug #129910.
Anyway, KDE not starting after an system upgrade seems a critical bug to
me.
--
KDE won't start after upgrade from feisty to gutsy RC1 an other surprises
https://bugs.launchpad.net/bugs/152110
You received
I had the same problem with a Core Duo T2500 after upgrading from edgy to
feisty. It is caused by a wrong default setting in
/etc/powersave/cpufreq
There is a line
CPUFREQD_MODULE=speedstep-centrino
telling the powersaved to just try to load the speedstep-centrino kernel module
which is the
