Ubuntu
ubiquity package

OS said that it crashed and wanted me to restart it

Bug #522951 reported by Conor D'Arcy on 2010-02-17

This bug report is a duplicate of: Bug #398614: XStartupError: X server exited with return code 1. 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 don't have any other info since I re-installed Ubuntu since this crash - just trying to get a screen resolution option higher than 800 x 600

ProblemType: Crash
Architecture: i386
Date: Tue Feb 16 21:16:48 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ubiquity-dm
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubiquity 2.0.8
ProcCmdline: /usr/bin/python /usr/bin/ubiquity-dm vt7 :0 hostname /usr/bin/ubiquity --only
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/bin/ubiquity-dm', 'vt7', ':0', 'hostname', '/usr/bin/ubiquity', '--only']
SourcePackage: ubiquity
Title: ubiquity-dm crashed with XStartupError in run()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

Tags:

Revision history for this message

Conor D'Arcy (conor-darcy) wrote on 2010-02-17:

Casper.gz Edit (760 bytes, application/x-gzip)
Traceback.txt Edit (293 bytes, text/plain; charset="utf-8")
UbiquityDebug.gz Edit (489 bytes, application/x-gzip)
UbiquityDm.gz Edit (649 bytes, application/x-gzip)
UbiquityPartman.gz Edit (2.2 KiB, application/x-gzip)
UbiquitySyslog.gz Edit (16.4 KiB, application/x-gzip)

Revision history for this message

Apport retracing service (apport) wrote on 2010-02-17: 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 #398614, 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.