This bug also effects System76. We think this is a race condition as described in bug #644638.
The bug is reproducible 100% of the time on fast hardware (particularly nVidia with SSD's). If we cause gdm to pause for 5 seconds, oem-config will run; however, gdm then starts in the background on VT1 while oem-config is on VT7.
We have tried a couple workarounds to no avail.
1.) pause GDM if /var/lib/oem-config/run exist. While this works to start oem-config, the user is dropped to an error message and a reboot is required to reach their login.
1.) exit GDM if /var/lib/oem-config/run exist. System doesn't boot.
It seems that Upstart's "start on starting gdm" isn't precise enough to ensure oem-config starts before GDM on fast hardware.
This bug also effects System76. We think this is a race condition as described in bug #644638.
The bug is reproducible 100% of the time on fast hardware (particularly nVidia with SSD's). If we cause gdm to pause for 5 seconds, oem-config will run; however, gdm then starts in the background on VT1 while oem-config is on VT7.
We have tried a couple workarounds to no avail.
1.) pause GDM if /var/lib/ oem-config/ run exist. While this works to start oem-config, the user is dropped to an error message and a reboot is required to reach their login. oem-config/ run exist. System doesn't boot.
1.) exit GDM if /var/lib/
It seems that Upstart's "start on starting gdm" isn't precise enough to ensure oem-config starts before GDM on fast hardware.