oem-config gtk frontend does not get displayed on first boot if two display managers are installed

Bug #926977 reported by Jamin W. Collins
6
This bug affects 1 person
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://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/650703
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/644638
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/812230

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-firstboot) recreates the problem.

I'm attempting to pin this down more definitively to locate exactly what within gdm's upstart definition is causing the issue.

Revision history for this message
Jamin W. Collins (jcollins) wrote :

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.

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
Revision history for this message
Jamin W. Collins (jcollins) wrote :

Any chance of getting an update or attention to this report?

Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 926977

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.