[Bug 779986] Re: system configuration (post-oem) crashes on user creation

[Launchpad Bug Tracker]

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

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

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

Title:
  system configuration (post-oem) crashes on user creation

Status in “ubiquity” package in Ubuntu:
  Confirmed
Status in Baltix GNU/Linux:
  New

Bug description:
  Binary package hint: ubiquity

  Configured machine, including the application of some company-specific
  password requirements, and then ran the oem pre-deployment config app.
  Created image & applied it to a new machine. Booted new machine, which
  (correctly) launched me into Ubiquity system configuration dialog. Set
  keyboard, time zone, etc.

  On user creation screen, it prompted for username, hostname, PW. Input
  a fairly weak password (tie3shoe) & the UI identified it as a weak
  password but allowed me to proceed.

  A series of small black status boxes appeared (note, as a side topic,
  that they stacked on top of each other rather than one replacing the
  other).

  When it got to the "creating user" status box, ubiquity abended & a
  new dialog appeared instructing me to file a bug.

  Upon examination of syslog, it was immediately apparent what the
  problem is. I'll cut-and-paste it here:

  May  9 10:26:49 ubu-1010-eb ubiquity: Weak password: based on a dictionary word and not a passphrase.
  May  9 10:26:49 ubu-1010-eb ubiquity: last message repeated 2 times
  May  9 10:26:49 ubu-1010-eb ubiquity: chpasswd: (user ragrady) pam_chauthtok() failed, error:
  May  9 10:26:49 ubu-1010-eb ubiquity: Authentication token manipulation error
  May  9 10:26:49 ubu-1010-eb ubiquity: chpasswd: (line 1, user ragrady) password not changed

  syslog then logs a series of the standard "here are the password
  rules, here's a password you can use if nobody's looking over your
  shoulder" messages, but none of that was visible to me via ubiquity.

  Ubiquity then crashes.

  I have confirmed on another machine that using a stronger password
  (i.e. one that actually conforms to the underlying pam requirements)
  allows ubiquity to create the user & finish successfully.

  This is on 10.10 with ubiquity/oem-config version 2.4.8

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