No OEM prompts appear after rebooting from an installation

Bug #62814 reported by Marc Tardif
4
Affects Status Importance Assigned to Milestone
oem-config (Ubuntu)
Fix Released
High
Colin Watson

Bug Description

After rebooting from an OEM installation of 20060927.7 alternate AMD64, there are no prompts for username, language, etc. Instead, there is a black screen with the "X" as the cursor.

On the console, there is text that looks like the expected prompts, ie "To create a user so that you can use your new system normally...". That is followed by the following error message:

  bash: no job control in this shell

Revision history for this message
Marc Tardif (cr3) wrote :

To be more precise, the problem occurs after running oem-config-prepare and rebooting. So, this is probably the same problem as #62648.

Also, higher on the console, there is more interesting information about the error:

File "/usr/sbin/oem-config-dm" line 47 in run (root_width, root_height) = root.get_size()
AttributeError: 'NoneType' object has no attribute 'get_size'

Revision history for this message
Simon Law (sfllaw) wrote :

oem-config-dm points out that it can't find the display. Perhaps it fires up before X is ready?

Changed in oem-config:
importance: Undecided → High
status: Unconfirmed → Confirmed
Colin Watson (cjwatson)
Changed in oem-config:
assignee: nobody → kamion
Revision history for this message
Colin Watson (cjwatson) wrote :

Yes, an strace supports Simon's theory. Rather than just increasing the sleep timeout, I'm trying to work out from gdm how to do this properly.

Revision history for this message
Colin Watson (cjwatson) wrote :

oem-config (1.7) edgy; urgency=low

  * Add oem-config-udeb/frontend question, defaulting to gtk; preseed this
    to install a different oem-config frontend on the target system (closes:
    Malone #62777).
  * Wait more or less properly by means of SIGUSR1 for the X server to start
    up, rather than arbitrarily sleeping for five seconds.
  * Don't actually import the frontend module in oem-config-dm; merely check
    whether it exists. Otherwise, at least gtk will try to contact the X
    server at import time and get very confused when it predictably isn't
    there (closes: Malone #62814).

 -- Colin Watson <email address hidden> Tue, 3 Oct 2006 22:04:48 +0100

Changed in oem-config:
status: Confirmed → Fix Released
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.