Ubuntu
ubiquity package

ubiquity crashed with RuntimeError in progress_loop()

Bug #534552 reported by Kevin Arnold on 2010-03-08

This bug report is a duplicate of: Bug #291287: ubiquity crashed with RuntimeError in progress_loop(). 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 have just installed Ubuntu when the sign came up with a crash report. The version is Ubuntu 8.10 I am new to this system.
Prior to this I was on Windows XP.
I allowed the install to use the whole of the hard drive.
Sorry if it's my fault.
Kev

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.5
Package: ubiquity 1.10.10
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity --only
ProcEnviron:
LANGUAGE=
PATH=/sbin:/bin:/usr/sbin:/usr/bin
LANG=en_US.UTF-8
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
SourcePackage: ubiquity
Title: ubiquity crashed with RuntimeError in progress_loop()
Uname: Linux 2.6.27-7-generic i686
UserGroups:

Tags:

Revision history for this message

Kevin Arnold (cellarmedic) wrote on 2010-03-08:

Casper.gz Edit (1.3 KiB, application/x-gzip)
Traceback.txt Edit (544 bytes, text/plain; charset="utf-8")
UbiquityDebug.gz Edit (966 bytes, application/x-gzip)
UbiquityDm.gz Edit (783 bytes, application/x-gzip)
UbiquityPartman.gz Edit (4.2 KiB, application/x-gzip)
UbiquitySyslog.gz Edit (14.5 KiB, application/x-gzip)

Revision history for this message

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