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.
** Summary changed: - KDM fails to launch X on edgy + KDM takes several minutes to start on Edgy ** Description changed: - 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. + 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. -- KDM takes several minutes to start on Edgy https://launchpad.net/bugs/59242 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs