oem-config-prepare seems to work but after rebooting the config doesn't start

Bug #720176 reported by Jean-Baptiste Lallement
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Critical
Unassigned
Lucid
New
Critical
Unassigned

Bug Description

Binary package hint: ubiquity

ISO Testing Lucid Alternate i386 20110211.3

After installation Lucid OEM, oem-config-prepare seems to run correctly. But when I restart, the user OEM is logged again and the config of the initial user doesn't start.

I attach the logs with the debug-oem-config kernel command line argument.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: ubiquity 2.2.25
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic i686
Architecture: i386
Date: Wed Feb 16 17:20:13 2011
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.3)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: ubiquity

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
Changed in ubiquity (Ubuntu):
importance: Undecided → Critical
tags: added: iso-testing
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I think this is a problem with upstart. If I boot in rescue mode instead of normal boot after the oem-config-prepare step, suddenly X starts, and the user configuration step begin.

Changed in ubiquity (Ubuntu Lucid):
importance: Undecided → Critical
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

If I boot with --verbose and without 'quiet splash' on the kernel command line, the boot is much slower and ubiquity starts as expected. This would suggest a race of some kind.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

A guess is that the upstart job for oem-config starts too early.
Removing the line
or stopping rc RUNLEVEL=[2345])

to force the job to start when gdm starts workaround the issue. This is just a suggestion and I don't know if its the right fix.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Now that enough information has been collected, I'm marking as dup of bug 650703 which is the same issue.

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.