ubiquity upstart: if ubiquity-dm fails to start for an unknown reason, init script exits with no error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
I've been having some issues with ubiquity-dm only starting intermittently on a custom livecd.
The problem as it turns out was that debconf was being locked by another init script, and this would cause ubiquity-dm to not start.
However, the provided upstart script ubiquity.conf was still exiting 'normally', ie with a 0 return code, despite ubiquity-dm failing to start.
Debugging with set -x in /etc/init/
...
+ [ -n ]
+ ubiquity-dm vt7 :0 ubuntu /usr/bin/ubiquity --greeter --only
debconf: DbDriver "config": /var/cache/
Traceback (most recent call last):
File "/usr/bin/
dm = DM(vt, display, username)
File "/usr/bin/
db = DebconfCommunic
File "/usr/lib/
write=
File "/usr/lib/
self.
File "/usr/lib/
self.version = self.version(2)
File "/usr/lib/
lambda *args, **kw: self.command(
File "/usr/lib/
status = int(status)
ValueError: invalid literal for int() with base 10: ''
+ [ ]
+ exit 0
Basically, there is an if statement that catches a couple of known conditions for ubiquity-dm not starting, but there is no catch-all to consider any other cases.
debian/
...
if ! ubiquity-dm vt7 :0 ubuntu /usr/bin/ubiquity $debug $automatic $choose $ldtp --only $frontend; then
# has X crashed, or has ubiquity?
if [ "$automatic" ] && ! [ -f /var/log/
# in case we crashed before the X startup sequence
fi
fi
I've attached a patch which simply inserts an 'else' catch-all.
Related branches
Changed in ubiquity (Ubuntu): | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
Changed in ubiquity (Ubuntu): | |
status: | Triaged → Fix Committed |
The attachment "ubiquity- debconflock. patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.
[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]