Moved this back to kdm - while I appreciate there is a "Upstart could be better" issue in here, there's more than enough of those filed upstream and I'm hard at work on the next version of Upstart -- there's no quick fix in Upstart for dealing with this kind of sequencing issue yet
The fix for this bug will come from changes to the kdm.conf - the purpose of the PRIMARY_DEVICE_FOR_DISPLAY was to avoid these races - perhaps that udev rule or the kdm config need tweaking to make sure that a device isn't tagged as such when using the nvidia binary driver?
Moved this back to kdm - while I appreciate there is a "Upstart could be better" issue in here, there's more than enough of those filed upstream and I'm hard at work on the next version of Upstart -- there's no quick fix in Upstart for dealing with this kind of sequencing issue yet
The fix for this bug will come from changes to the kdm.conf - the purpose of the PRIMARY_ DEVICE_ FOR_DISPLAY was to avoid these races - perhaps that udev rule or the kdm config need tweaking to make sure that a device isn't tagged as such when using the nvidia binary driver?