Race between upstart and non-upstart init scripts.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Karmic |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: ubiquity
When trying to boot up to only-ubiquity or automatic-ubiquity, it appears that X crashes for some reason or another. As soon as this happens, gdm starts up (with a working X) and ubiquity launches into noninteractive - proceeding to fill up the livefs unless you kill ubiquity very quickly from within gdm.
Oddly enough, if you boot into text mode and THEN start ubiquity-dm, things work properly.
ProblemType: Crash
Architecture: i386
Date: Thu Oct 22 03:56:46 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
Package: ubiquity 2.0.2
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: ubiquity
Title: ubiquity-dm crashed with XStartupError in run()
Uname: Linux 2.6.31-14-generic i686
UserGroups:
XsessionErrors:
(gnome-
(gnome-
(nautilus:5896): Eel-CRITICAL **: eel_preferences
(polkit-
Changed in ubiquity (Ubuntu Karmic): | |
status: | New → Fix Committed |
Ignore UbiquityDebug.gz. It's not valid because that's what started getting ran from ubiquity noninteractive.