Dammit! Launchpad ate my comment with #109... Ok, typing it up again I think I have a fix that I like. I added a debian patch (40_initial_server_on_vt7-improve-timing.patch see #109) What happens is that I moved the creation of the signal file (/var/run/gdm/firstserver.stamp) to the emit_ready_idle handler. This appears to work on my system:
Having seen some of the fastest boots, X always landed on vt7 safely. Also, vt7 is on the commandline parameters. I have seen evidence in Xorg.*.log that this appeared to work even though I had four X session launch attempts within about a second (the first failing because of nvidia not being around). I have uploaded a snapshot package to a temp ppa for any interested testers: https://launchpad.net/~bugs-sehe/+archive/gdm625239. Please allow some time for the build server to complete the binaries Note: I'm not a debian dev, I don't know about their codeing standards. I leave it to you to review/incorporate any of this as you like. I haven't actually even studied the code mouch to explain whether/why this should work, I just tried and it seemed to do the trick :) Cheers Seth -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
