Okay our investigation showed that, empirically, once upstart has started a job (like gdm), no other job can stop it, even if it is (starts on) for that job. Actually this means that a system with gdm, kdm etc. installed they will all fight for a VT and the first one will get it, however this is a fairly rare setup (installer will never create it).
Our fix was pretty dumb, we added the same check to proceed in oem- config.conf as an exit into gdm.conf, after the 'script' marker: if [ -f /var/lib/oem-config/run ] then exit 0 fi This way gdm will not start while oem-config is scheduled to run. Since oem-config tries to reboot afterwards this is fine and dandy. We got the same crash as Rob here, attached. There are some errors about config-2.6.31.14-efikamx not existing: that's because we don't have a kernel package, only tar archives, so it's a hack. An initrd was created for us (yay!) successfully. I am not sure what ubiquity is trying to do here at all.. FYI for Oliver (and maybe rsalveti), "sudo oem-config-prepare quiet" is safe to run to make oem-config start on the next boot. All it does apart from checking if you're running a desktop and finding the right front- end (which it does properly here) is set the /var/lib/oem-config/run file. ** Attachment added: "syslog for ubiquity crash" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/644638/+attachment/1627965/+files/syslog -- maverick oem-config gtk frontend does not start on first boot because gdm runs before it https://bugs.launchpad.net/bugs/644638 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
