/home/oem and oem user are not removed by oem-config-firstboot

Bug #1554194 reported by Jason Gerard DeRose on 2016-03-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)

Bug Description

Sometime recently during Xenial development, oem-config has become quite broken.

It seems the underlying problem is that the "oem" user and the "/home/oem" folder aren't getting removed by oem-config-firstboot.

Steps to reproduce:

1) Do an OEM-mode install from the latest Xenial daily ISO

2) Click "Prepare for shipping to end user"

3) No matter what option you choose during the user firstrun config (automatic login, require password to login, or require password to login plus encrypt home directory), the "oem" user and the "/home/oem" folder will still exists, and the user will get logged into the "oem" account after completing the firstrun config.

Note that the oem-config* packages seem to be removed okay... just the "oem" user itself isn't getting removed.


ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 7 14:33:12 2016
InstallationDate: Installed on 2016-03-07 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Jason Gerard DeRose (jderose) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers