oem-config: networking not enabled during user config

Bug #1508865 reported by Jason Gerard DeRose on 2015-10-22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
ubiquity (Ubuntu)
Mathieu Trudel-Lapierre

Bug Description

After clicking "Prepare for shipping to end user" and rebooting, Ubiquity does not have networking enabled.

When on Ethernet, Ubiquity should have networking enabled and should use it to guess your timezone. When not on Ethernet and you have a WiFi card, Ubiquity should prompt you to join a WiFi network. Neither of these are happening.

Thanks to Martin Wimpress for catching this!

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: oem-config 2.21.37
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Oct 22 04:04:14 2015
InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=7ce2ecc1-7dab-4a39-b74a-66776a98de13 ro quiet splash vt.handoff=7
PackageArchitecture: all
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Jason Gerard DeRose (jderose) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
description: updated
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Changed in ubiquity (Ubuntu):
importance: Undecided → High
Changed in hundredpapercuts:
status: New → Confirmed
importance: Undecided → High
Michel-Ekimia (michel.ekimia) wrote :

We just show this for our first 15.10 shipped computer.

Yes this is important I think.

Jason Gerard DeRose (jderose) wrote :

Just to clarify what the behaviour is with 14.04.4, what the behaviour used to be up till 15.10.

After an OEM install and clicking "Prepare for shipping to end user", on the next boot 14.04.4 will:

1. Automatically enabled wired networking when connected over Ethernet, or

2. When not connected over Ethernet and you have WiFi hardware, the 2nd screen/page will be a prompt to join a WiFi network

When you get to the timezone page/screen, networking is enabled if you're on Ethernet or have WiFi hardware available and connected to a WiFi network. When networking is enabled, Ubiquity will use this to guess your timezone based on IP address. When networking is not available, the timezone will always be initially set to the default of US/Eastern.

Currently on 14.04.4 the nm applet is always shown (well, is always shown when you have at least some networking hardware available... not sure what it does when there is no networking hardware). Although I swear that right before 15.10 was released, 14.04.3 would only show the nm applet when you had WiFi hardware available but weren't on Ethernet... but I could be mistaken about that.

With up-to-date 15.10 or Xenial, this is the behaviour:

1. The nm applet is never shown

2. When on Ethernet, networking is not enabled; when not on Ethernet but you have WiFi hardware available, you are not prompted to join a WiFi network

3. After the language and keyboard selection screen, Ubiquity always goes directly to the timezone selection screen; as networking is not enabled, Ubiquity can't guess your timezone, so the timezone will always be set to the default of US/Eastern

Changed in ubiquity (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.21.53

ubiquity (2.21.53) xenial; urgency=medium

  * debian/oem-config.install: install systemd units to /usr/lib/oem-config
    instead of the systemd paths. (LP: #1552621)
  * bin/oem-config-prepare: install systemd job from our copy in
  * bin/oem-config-wrapper: remove our special systemd units after oem config
    is completed.
  * debian/oem-config.target: Wants= network-manager.service too; so we can
    get online and possibly do NTP, downloads, etc. (LP: #1508865)

 -- Mathieu Trudel-Lapierre <email address hidden> Mon, 28 Mar 2016 22:53:30 -0400

Changed in ubiquity (Ubuntu):
status: In Progress → Fix Released
Jason Gerard DeRose (jderose) wrote :

Mathieu, thanks a million for fixing this! I'll test it ASAP!

Jason Gerard DeRose (jderose) wrote :


Everything seems solid with this fix. I confirmed that:

1. When plugged into Ethernet, the NM applet is show, networking is enabled, and ubi-timezone correctly guesses your timezone

2. When *not* plugged into Ethernet but you have WiFi hardware, the NM applet is shown, oem-config prompts you to join a WiFi network, and, if you do, ubi-timezone correctly guesses your timezone

3. When not plugged into Ethernet and you have WiFi hardware but choose *not* to connect to any WiFi network, everything still works as expected (understandably, ubi-timezone can't guess your timezone in this case)


Paul White (paulw2u) wrote :

Closing Papercuts task as fixed in Ubuntu some time ago

Changed in hundredpapercuts:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers