I had to post for a kdm issue in intrepid, but I also recently started experiencing on my desktop running 8.o4. Not sure if this should go to the kde4 sub forum as my login manager is kdm-kde4, although I can't get gdm or kdm (kde3) to work either. Boots fine, and then blackness... ctrl+alt+f1 brings me to console (two identical lines occur "can't open display," then I can login and run /etc/init.d/kdm-kde restart, and I get a notice that kdm is not running, it starts and I can log in that way.
It is an asus eee-box desktop and sometime about dual pipelines make the xserver think there are two displays so adding a line to xorg is supposed to fix that by telling it to ignore lvds, but it doesn't and I get a black screen anyway... and since kde4 can't handle dual screens in hardy, the desktop looks like two once I get there.
I have tried purging kdm-kde4, using kdm regular with the kde4 package removed, I have tried having all three 9including gdm) and using dpkg-reconfigure to select different ones. I get ONE full regular reboot after doing any of these things... then back to black on the next boot. Fortunately suspend works on my machine so I don't have to reboot that often.
Suggestions beyond this... part of me thinks the xserver is not starting to begin with or is locking up.
It was working fine and suddenly this behavior started.
It is an asus eee-box desktop and sometime about dual pipelines make the xserver think there are two displays so adding a line to xorg is supposed to fix that by telling it to ignore lvds, but it doesn't and I get a black screen anyway... and since kde4 can't handle dual screens in hardy, the desktop looks like two once I get there.
I have tried purging kdm-kde4, using kdm regular with the kde4 package removed, I have tried having all three 9including gdm) and using dpkg-reconfigure to select different ones. I get ONE full regular reboot after doing any of these things... then back to black on the next boot. Fortunately suspend works on my machine so I don't have to reboot that often.
Suggestions beyond this... part of me thinks the xserver is not starting to begin with or is locking up.
It was working fine and suddenly this behavior started.
Comment