[Bug 1413521] Re: oem config not shown first boot

Mathieu Trudel-Lapierre mathieu.tl at gmail.com
Wed Feb 18 17:49:01 UTC 2015


Did the installer ask you for an OEM identifier at the beginning of the
installation? I've seen some cases already where it looks like you're
doing an OEM installation, but there are only few differences between
both OEM and a standard install, so the resulting installed system does
not include oem-config.

Ways to notice are the OEM identifier that is requested early in the
installation process, and the fact that the installer will ask for a
generic username and password rather than pre-filling prompts with the
'oem' username, for example.

If you could attach /var/log/installer/syslog from the resulting install
(or /var/log/syslog from the installation process), this could help in
identifying where things went wrong.

Thanks!

** Changed in: ubiquity (Ubuntu Vivid)
       Status: New => Incomplete

-- 
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/1413521

Title:
  oem config not shown first boot

Status in ubiquity package in Ubuntu:
  Incomplete
Status in ubiquity source package in Vivid:
  Incomplete

Bug description:
  On Kubuntu Vivid Alpha2 i386, after a successful oem install, has no oem-config utility anywhere.
  There is no icon on the desktop, or in the menu's, to launch the final setup program.
  Thus effectively there is no way to complete the installation.

  Ubuntu:      Vivid Vervet (15.04)
  Arch:            i386
  Ubiquity:    2.21.5

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



More information about the foundations-bugs mailing list