oem-config fails to remove oem user

Bug #1219273 reported by Jason Gerard DeRose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
System76
Triaged
Critical
Unassigned
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

oem-config is currently broken on Saucy. The problem seems to be that the "oem" user does not get removed, so you end up auto-loging into the "oem" account every time you boot, even though oem-config seeems to have sucesfully created the customer's user account.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: oem-config (not installed)
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Sat Aug 31 11:45:13 2013
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=us keyboard-configuration/variantcode=dvorak oem-config/enable=true
InstallationDate: Installed on 2013-08-31 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130830)
MarkForUpload: True
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jason Gerard DeRose (jderose) wrote :
Changed in system76:
importance: Undecided → Critical
status: New → Triaged
description: updated
description: updated
Revision history for this message
Jon Arnold (jonarnoldsemail) wrote :

Is it safe to delete the user?

I don't know the user password for the OEM user.

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.