[Bug 926977] [NEW] oem-config gtk frontend does not start on first boot because gdm runs before it

[Jamin W. Collins]

Public bug reported:

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.

** Affects: ubiquity (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/926977

Title:
  oem-config gtk frontend does not start on first boot because gdm runs
  before it

Status in “ubiquity” package in Ubuntu:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/926977/+subscriptions