[Bug 1007285] [NEW] oem-config stopped (upstart) when multiple graphical manager are installed

[Thomas Sondag]

Public bug reported:

On Oneiric  with oem-config  2.8.7
If I install only oem-config it's also installing kdm (but I'm keeping lighdm as my default display manager)
After running oem-config-prepare the system will start always start ligthdm and not oem-config.

This is due to the oem-config.conf upstart script stop on condition.

When both lightdm and kdm are installed on the same system, they are started at the same time (almost) by upstart, the starting event is sent and the oem-config is started. 
Then lightdm and kdm are looking in the /etc/X11/default-display-manager to see who is going to be used (lightdm in my stituation), so kdm will be stoped and upstart will send the kdm stopping event, caught by oem-config stop on condition and oem-config will be stopped and lightdm will be started.

So the stop condition should be modified or removed (why do we need a
stop condition on a task ?) but I'm not really good at upstart so far :)

if I install oem-config with ubiquity-frontend-gtk it doesn't install
kdm and everything is works just fine.

Best regards,
  Thomas

** 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/1007285

Title:
  oem-config stopped (upstart) when multiple graphical manager are
  installed

Status in “ubiquity” package in Ubuntu:
  New

Bug description:
  On Oneiric  with oem-config  2.8.7
  If I install only oem-config it's also installing kdm (but I'm keeping lighdm as my default display manager)
  After running oem-config-prepare the system will start always start ligthdm and not oem-config.

  This is due to the oem-config.conf upstart script stop on condition.

  When both lightdm and kdm are installed on the same system, they are started at the same time (almost) by upstart, the starting event is sent and the oem-config is started. 
  Then lightdm and kdm are looking in the /etc/X11/default-display-manager to see who is going to be used (lightdm in my stituation), so kdm will be stoped and upstart will send the kdm stopping event, caught by oem-config stop on condition and oem-config will be stopped and lightdm will be started.

  So the stop condition should be modified or removed (why do we need a
  stop condition on a task ?) but I'm not really good at upstart so far
  :)

  if I install oem-config with ubiquity-frontend-gtk it doesn't install
  kdm and everything is works just fine.

  Best regards,
    Thomas

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