This bug was fixed in the package ubiquity - 2.21.18
---------------
ubiquity (2.21.18) vivid; urgency=medium
* Overhaul for proper systemd support (LP: #1436937)
* bin/oem-config-prepare: set the systemd default target to oem-config.target
instead of using /var/lib/oem-config/run as a flag.
* bin/oem-config-firstboot:
- after removing the oem user, set the default target back to graphical.
- call for systemd to start the graphical target, so as to complete booting
to graphical or to TTYs after oem-config-firstboot has run.
* debian/oem-config.target: create a new target for oem-config so that it can
start without conflicting with a display-manager that may also want to
start and use the oem user in auto-login.
* debian/oem-config.oem-config.service: simplify the service's start
conditions; we don't really need to worry about Before/After since we'll
run in our own isolated target.
* debian/oem-config.install: force the installation of the new target in the
right location for systemd.
-- Mathieu Trudel-Lapierre <mathieu...@ubuntu.com> Thu, 02 Apr 2015 13:58:02
-0400
** Changed in: ubiquity (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436937
Title:
Temporary OEM user not removed after end user setup
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1436937/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
