oem-config gtk frontend does not get displayed on first boot if two display managers are installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
This problem has been reported a number of times in the past:
https:/
https:/
https:/
While the past reports are listed as fixed, the problem is still present in Oneric if gdm is installed prior to running the oem-config-prepare command and rebooting.
I've confirmed that this is indeed linked to gdm being installed, as simply moving (or removing) the /etc/init/gdm.conf upstart definition from /etc/init/ rectifies the problem. While restoring the file and rebooting (without completing the user configuration from oem-configure-
I'm attempting to pin this down more definitively to locate exactly what within gdm's upstart definition is causing the issue.
summary: |
- oem-config gtk frontend does not start on first boot because gdm runs - before it + oem-config gtk frontend does not get displayed on first boot if two + display managers are installed |
In further testing, I've moved the lightdm upstart definition out of the way and updated /etc/X11/ default- window- manager to point to /usr/sbin/gdm. This also rectifies the problem.
Simply having both upstart definitions present seems to create the problem. Going to test with additional DMs to see if the problem persists as long as there are two DM upstart definitions present.