KDM takes several minutes to start on Edgy

Bug #59242 reported by Rocco Stanzione
8
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

If kdm is my display manager, I get no X on startup after upgrading to edgy. Starting it manually looks fine in the console - kdm says it's starting and there are no error message. But X never starts. There's no Xorg.0.log, no flicker, no indication that X is trying to start. I uncommented the debug line in the kdm init script, but I still get no output. Switched to gdm as a workaround.
UPDATE: if I give KDM several minutes to start, it does. It seems to be waiting for something to timeout.

Revision history for this message
Lothar Braun (typecast) wrote :

Can you try to switch to tty1 (Strg+Alt+F1) and then back to tty7 (Strg+Alt+F7).

Does kdm start up then?

Revision history for this message
Rocco Stanzione (trappist) wrote :

I tried that several times, thinking that maybe X was starting but I just wasn't being switched to tty7. I don't think I ever tried to start kdm *from* tty7, though, if that's what you mean?

Revision history for this message
Lothar Braun (typecast) wrote :

No, i did just mean that you should switch between tty1 and tty7. I asked you to to that, because i have a similar problem: KDM doesn't start up after the splash screen appears. Switching to tty1 and back to tty7 brings kdm up.

Revision history for this message
Rocco Stanzione (trappist) wrote :

Ah yeah, that didn't do the trick here.

Revision history for this message
Kay Hayen (kayhayen) wrote :

I can confirm the bug. My edgy system displays a black screen after boot. When I press ALT, I see the login screen of tty1. Then when I press ALT-F7 it will start X and kdm will run normally.

Revision history for this message
Rocco Stanzione (trappist) wrote :

I switched to GDM as a workaround, which works fine. Seems to be a kdm-specific bug.

Changed in kdebase:
status: Unconfirmed → Confirmed
Revision history for this message
geh (geh) wrote :

I can confirm the bug too. Pressing ctrl-alt-f7 after usplash disappears launches KDM.

Revision history for this message
geh (geh) wrote :

I have solved the problem for me: I upgraded to edgy without upgrading to upstart , because I had removed the packages ubuntu-minimal and ubuntu-base.
So, I reinstalled those, and at the next boot KDM showed up as expected.

Revision history for this message
Kay Hayen (kayhayen) wrote :

Thank you Guillaume, after executing apt-get install ubuntu-minimal I also found that I was still on the old sysvinit and not upstart.

Now the problem is gone for me too.

Revision history for this message
Lothar Braun (typecast) wrote :

Rocco: Does Guillaume's tip help you, too?

Revision history for this message
Rocco Stanzione (trappist) wrote :

I'm afraid not. Looks like there's no such package as ubuntu-base anymore. I did reinstall ubuntu-minimal, some dependencies of which hadn't been installed, including upstart-logd, but reinstalling didn't help. I did notice something potentially helpful, though. When I start kdm, nothing seems to happen. When I try to stop it, it says it's not running because there's no pid file, but there's a kdm process and a kdm-config process that I have to kill manually.

Revision history for this message
Rocco Stanzione (trappist) wrote :

I tried again, to see what I could see about those two processes. I attached to each of them with strace and saw no activity. The kdm process seemed to be hung up on a read. Peeked at the xorg log, saw nothing interesting. I was just about to switch back to gdm when bam, I got an nvidia splash screen. This probably took about 2 minutes. It also took longer than usual (not sure how long, I went out to smoke) to get past the bare X screen with that "x" cursor. I've seen some similar behavior on Gnome desktops when there's a firewall blocking invalid packets regardless of source (Gnome generates a lot of that on lo, it looks like) but I'm not running Gnome and not running a firewall on this box. I've also seen similar stuff when lo is down, which it's not here. I'm going to change the description of this bug.

description: updated
Revision history for this message
Ralph Janke (txwikinger) wrote :

Edgy is not supported anymore and this problem does not seem to have ever occurred on any successive release. If this problem can be reproduced on hardy, please re-open with the necessary information.

Thanks

Changed in kdebase:
importance: Undecided → Medium
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.