@Steve:
I've taken the trouble to install maverick beta (64bit). I installed on
the same iron, same disk configuration (2x SSD in raid0, lvm2 root).
After doing the server install I installed ubuntu-desktop and bootchart.
My few boots took max 5.71s in bootchart (woah) and all my X desktops
were 'first time right' (with the explicit vt7 param visible in ps -ef).
So that seems to imply that the problem does not manifest itself on
maverick (yet). However, since we have such good understanding of the
triggering events I decided to check with my force.sh (forced
reproduction script from comment #142).
Surprisingly, not only is the new nvidia/xorg combination vulnerable to
the same start up race, what's more: the timing has gotten faster by
just enough that gdm-simple-slave (gdm-server.c) runs out of launching
attempts. The end result in that scenario is _not pretty_: the upstart
job ("task"?) is in status 'running' while there is no X session at all!
All in all, it appear that the potential that this race occurs on
Maverick is present just like in Ubuntu. Timings are different, and I
haven't yet spontaneously encountered the situation on boot. But on
manual triggering the behaviour is far worse.
Attached is the output of running force.sh on maverick (completely
uptodate as of now)
** Attachment added: "maverick.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/625239/+attachment/1585932/+files/maverick.log
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
