system configuration (post-oem) crashes on user creation

[rossgrady]

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

[Brian Murray (brian-murray)]

Exception during installation:
May 9 10:26:49 ubu-1010-eb python: Traceback (most recent call last):
May 9 10:26:49 ubu-1010-eb python: File "/usr/share/ubiquity/plugininstall.py", line 1424, in <module>
May 9 10:26:49 ubu-1010-eb python: install.run()
May 9 10:26:49 ubu-1010-eb python: File "/usr/share/ubiquity/plugininstall.py", line 54, in wrapper
May 9 10:26:49 ubu-1010-eb python: func(self)
May 9 10:26:49 ubu-1010-eb python: File "/usr/share/ubiquity/plugininstall.py", line 138, in run
May 9 10:26:49 ubu-1010-eb python: self.configure_plugins()
May 9 10:26:49 ubu-1010-eb python: File "/usr/share/ubiquity/plugininstall.py", line 360, in configure_plugins
May 9 10:26:49 ubu-1010-eb python: raise install_misc.InstallStepError("Plugin %s failed with code %s" % (plugin.NAME, ret))
May 9 10:26:49 ubu-1010-eb python: InstallStepError: Plugin usersetup failed with code 1
May 9 10:26:49 ubu-1010-eb python:

[Launchpad Janitor (janitor)]

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

[Mantas Kriaučiūnas (mantas)]

Ubuntu 12.04 (precise) oem-config also has this issue if user enters weak password in oem-config phase, then oem-config phase newer ends :(
I can send a log file, but I think you don't need it, because bug is very easy to reproduce - simply enter a weak password, for example one letter :)

[Karim Hosein (khosein)]

Also with "fair" passwords.

I will attempt a strong password and see.

[Karim Hosein (khosein)]

Also with "good" and "strong" passwords.

Both the "Good" and "Strong" passwords had at least ONE UPPER, one lower and 1 numb3r and the "Strong" also contained 1 speci@l character.

Funny thing is, the "good" password contained no dictionary words.

GOOD= Ua33917RT
STRONG= Bl@st Away 283

[Marcus Tomlinson (marcustomlinson)]

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

[Marcus Tomlinson (marcustomlinson)]

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.