Ubuntu
ubiquity package

ubiquity crashed with InstallStepError in configure_user()

Bug #465045 reported by deefburger on 2009-10-30

This bug report is a duplicate of: Bug #258603: ubiquity crashed with InstallStepError in configure_user(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ubiquity (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: ubiquity

I'm installing 9.10 x86_64 into /dev/sda multiboot system with 9.10 beta on /dev/sdb

I also included the migration of my /sdb home directory which is unencrypted.

I will try without migration.....

ProblemType: Crash
Architecture: amd64
Date: Fri Oct 30 08:46:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: ubiquity 2.0.6
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/4036/environ'
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with InstallStepError in configure_user()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

Tags:

Revision history for this message

deefburger (clwatson) wrote on 2009-10-30:

Casper.gz Edit (810 bytes, application/x-gzip)
Traceback.txt Edit (946 bytes, text/plain; charset="utf-8")
UbiquityDebug.gz Edit (661 bytes, application/x-gzip)
UbiquityPartman.gz Edit (17.0 KiB, application/x-gzip)
UbiquitySyslog.gz Edit (51.3 KiB, application/x-gzip)

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-03: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #258603, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.