ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32"

Bug #577302 reported by Peter Clark
40
This bug affects 7 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

When installing Kubuntu with the option set for an encrypted $HOME, I get to the "Creating user" stage and I get this error:
---
Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 524, in <module>
    main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 509, in main
    install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 242, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 460, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 863, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 2566, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 388, in run
    self.configure_plugins()
  File "/usr/share/ubiquity/install.py", line 1088, in configure_plugins
    raise InstallStepError("Plugin %s failed with code %s" % (plugin.NAME, ret))
InstallStepError: Plugin usersetup failed with code 32

---
However, when I install Kubuntu without setting the option for encrypted $HOME, it installs successfully. I have tried searching both the ubiquity source and the ecryptfs source for code 32, but without any luck.

Revision history for this message
Peter Clark (mla-forrussia) wrote :
Revision history for this message
Peter Clark (mla-forrussia) wrote :

Here is the relevant portion of /var/log/syslog, although it doesn't seem to report much more than what was in the original error message. One thing of note are the lines:
---
May 8 09:50:56 ubuntu user-setup: WARNING: [/dev/sda3] does not appear to be swap space, skipping.
May 8 09:50:56 ubuntu user-setup: WARNING: There were no usable swap devices to be encrypted. Exiting.
May 8 09:50:57 ubuntu user-setup: mount: mount point /dev/shm does not exist
---
/dev/sda3 is definitely my swap partition. It may be worth noting that my older Kubuntu install (Hardy) encrypts the swap space.

Revision history for this message
Arthur Lutz (arthur-lutz) wrote :

I commented out the encrypted swap part in /usr/lib/ubiquity/user-setup/user-setup-apply so make sure that wasn't the source of the problem. I seem to get the same error.

I guess the problem is the "mount point /dev/shm does not exist" ... has anyone found the origin of the "32" ?

Revision history for this message
Arthur Lutz (arthur-lutz) wrote :

I ended up on the conclusion that the mounting of /dev and /proc was not done when trying to do the adduser which uses /dev/urandom for generating the encrypted passphrase.

Here is patch that got it work for me. I admit that it's probably a workaround because I didn't manage to find why /dev and /proc were not mounted as they should at that point.

tags: added: patch
Revision history for this message
Peter Clark (mla-forrussia) wrote :

I finally got around to testing the patch, and I'm pleased to say that it works. Merci beaucoup, Alex!

Revision history for this message
Twisted Lincoln, Inc. (twistedlincoln) wrote :

I experience this issue when using Remastersys on the standard Ubuntu -- Ubiquity will crash when run from the generated ISO and encrypted home directory support is chosen.

The patch listed by Arthur Lutz on comment #4 appears to have fixed the issue for me as well.

Revision history for this message
Brian Murray (brian-murray) wrote : Traceback

Exception during installation:
May 8 09:50:57 ubuntu python: Traceback (most recent call last):
May 8 09:50:57 ubuntu python: File "/usr/share/ubiquity/install.py", line 2566, in <module>
May 8 09:50:57 ubuntu python: install.run()
May 8 09:50:57 ubuntu python: File "/usr/share/ubiquity/install.py", line 388, in run
May 8 09:50:57 ubuntu python: self.configure_plugins()
May 8 09:50:57 ubuntu python: File "/usr/share/ubiquity/install.py", line 1088, in configure_plugins
May 8 09:50:57 ubuntu python: raise InstallStepError("Plugin %s failed with code %s" % (plugin.NAME, ret))
May 8 09:50:57 ubuntu python: InstallStepError: Plugin usersetup failed with code 32
May 8 09:50:57 ubuntu python:

tags: added: installer-crash
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
matt nimmo (maddness69) wrote :

this might be a dumb question but i have the same problem as desc. above however I'm new to ubuntu so how do actually apply the patch shown above
thanks

tags: added: oneiric
Revision history for this message
Gordo (iuventus4) wrote : Re: [Bug 577302] Re: ubiquity crashes with error: "InstallStepError: Plugin usersetup failed with code 32"

On Sun, Apr 15, 2012 at 1:40 PM, Fabio Marconi <email address hidden>wrote:

> ** Tags added: oneiric
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (982463).
> https://bugs.launchpad.net/bugs/577302
>
> Title:
> ubiquity crashes with error: "InstallStepError: Plugin usersetup
> failed with code 32"
>
> Status in “ubiquity” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: ubiquity
>
> When installing Kubuntu with the option set for an encrypted $HOME, I get
> to the "Creating user" stage and I get this error:
> ---
> Traceback (most recent call last):
> File "/usr/lib/ubiquity/bin/ubiquity", line 524, in <module>
> main(oem_config)
> File "/usr/lib/ubiquity/bin/ubiquity", line 509, in main
> install(args[0], query=options.query)
> File "/usr/lib/ubiquity/bin/ubiquity", line 242, in install
> ret = wizard.run()
> File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 460, in run
> self.progress_loop()
> File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 863, in
> progress_loop
> (ret, realtb))
> RuntimeError: Install failed with exit code 1
> Traceback (most recent call last):
> File "/usr/share/ubiquity/install.py", line 2566, in <module>
> install.run()
> File "/usr/share/ubiquity/install.py", line 388, in run
> self.configure_plugins()
> File "/usr/share/ubiquity/install.py", line 1088, in configure_plugins
> raise InstallStepError("Plugin %s failed with code %s" %
> (plugin.NAME, ret))
> InstallStepError: Plugin usersetup failed with code 32
>
> ---
> However, when I install Kubuntu without setting the option for encrypted
> $HOME, it installs successfully. I have tried searching both the ubiquity
> source and the ecryptfs source for code 32, but without any luck.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/577302/+subscriptions
>

I understand this is a duplicate bug from your first email.

On the third attempt at a fresh install, I did not select "Encrypt home
directory", and
the installation ran successfully to completion.

I can live without an encrypted home directory on this particular machine.

Thank you for your time and prompt attention.

Revision history for this message
Arthur Lutz (Logilab) (arthur-lutz-logilab) wrote :

Am using this patch to fix what seems to be the same bug in precise... how come it was not integrated ?

Revision history for this message
Thomas Weissel (valueerror) wrote :

unfortunately the patch fails on all my installations ob kubuntu 12.04 .. 1 out of 3 hunks failed to apply...

is it possible to fix this somehow on a live usb installaiton .. tell the system to mount /dev/ first.. or use the /preseed/custom.seed file to seed those random numbers ??

this error totally blocks the bootprocess on some machines for up to 5 minutes..

Revision history for this message
Arthur Lutz (Logilab) (arthur-lutz-logilab) wrote :

I believe this problem comes back on 12.04 because /dev/shm is now a link to /run/shm and when mount --bind of /dev/ is done the installer should also mount /run/shm

Revision history for this message
dino99 (9d9) wrote :

This version has expired

Changed in ubiquity (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.