Ubuntu
ubiquity package

ubiquity crashed with IOError in chroot_setup()

Bug #543804 reported by larry stevens on 2010-03-21

This bug report is a duplicate of: Bug #89463: Crash: Error removing mouseemu. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: ubiquity

nome-terminal: /usr/bin/gnome-terminal

We followed the directions below. the line above this one is what it says is the package.

ProblemType: Crash
Architecture: amd64
Date: Sun Mar 21 18:55:08 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
Package: ubiquity 2.0.6
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity --only
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
SourcePackage: ubiquity
Title: ubiquity crashed with IOError in chroot_setup()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

Tags:

Revision history for this message

larry stevens (larry-stevens48) wrote on 2010-03-21:

Casper.gz Edit (778 bytes, application/x-gzip)
Traceback.txt Edit (1017 bytes, text/plain; charset="utf-8")
UbiquityDebug.gz Edit (1.1 KiB, application/x-gzip)
UbiquityDm.gz Edit (1013 bytes, application/x-gzip)
UbiquityPartman.gz Edit (4.5 KiB, application/x-gzip)
UbiquitySyslog.gz Edit (196.2 KiB, application/x-gzip)

Revision history for this message

Apport retracing service (apport) wrote on 2010-03-26: 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 #292249, 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.