ubiquity fail

Bug #1131427 reported by Phill Whiteside
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Medium
Unassigned
ubiquity (Ubuntu)
New
Medium
Unassigned

Bug Description

testing a bug with xnox

i am filing a retrieve crash from the vm

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.13.12
ProcVersionSignature: Ubuntu 3.8.0-7.14-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CasperVersion: 1.330
Date: Thu Feb 21 20:20:13 2013
ExecutablePath: /usr/bin/ubiquity-dm
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
InterpreterPath: /usr/bin/python3.3
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130221.1)
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/ubiquity-dm vt7 :0 hostname /usr/bin/ubiquity --greeter --only
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
PythonArgs: ['/usr/bin/ubiquity-dm', 'vt7', ':0', 'hostname', '/usr/bin/ubiquity', '--greeter', '--only']
SourcePackage: ubiquity
Title: ubiquity-dm crashed with ValueError in command(): invalid literal for int() with base 10: ''
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Phill Whiteside (phillw) wrote :
information type: Private → Public
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

From UbiquityDM it looks like compiz / decorators crashed bringing everything down.

tags: removed: need-duplicate-check
Changed in compiz (Ubuntu):
importance: Undecided → Medium
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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