Upstart nightly doesn't boot Ubuntu Touch

[Ted Gould]

Upgrading my upstart to the version in the nightly PPA causes both my Nexus 4 and an emulator not to boot. Not sure of the reason though. Brain dumping here before EOD.

[Ted Gould (ted)]

It seems like lxc-android-boot gets locked on "initctl emit android", and I think that's because there's jobs that are "start on adroid and started bus" but dbus hasn't started. DBus seems like it should start after mountall had mounted local filesystems, but not sure why that isn't getting emitted.

[Ted Gould (ted)]

# apt-cache policy upstart
upstart:
  Installed: 1.12.1+1637+1568+201406121433~ubuntu14.10.1
  Candidate: 1.12.1+1637+1568+201406121433~ubuntu14.10.1
  Version table:
 *** 1.12.1+1637+1568+201406121433~ubuntu14.10.1 0
        500 http://ppa.launchpad.net/canonical-foundations/upstart-daily/ubuntu/ utopic/main i386 Packages
        100 /var/lib/dpkg/status
     1.12.1-0ubuntu8 0
        500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages

[James Hunt (jamesodhunt)]

Cannot recreate. I am using image 108 and have tested with both:

- lp:upstart manual build
- ppa:canonical-foundations/upstart-daily...

$ apt-cache policy upstart
upstart:
  Installed: 1.12.1+1638+1574+201406271556~ubuntu14.10.1
  Candidate: 1.12.1+1638+1574+201406271556~ubuntu14.10.1
  Version table:
 *** 1.12.1+1638+1574+201406271556~ubuntu14.10.1 0
        500 http://ppa.launchpad.net/canonical-foundations/upstart-daily/ubuntu/ utopic/main i386 Packages
        100 /var/lib/dpkg/status
     1.12.1-0ubuntu11 0
        500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages

[James Hunt (jamesodhunt)]

Since lp:upstart hasn't changed since 12 June 2014, this issue must have been caused by either:

a) A race in the Upstart async code (that code is currently being reviewed).

b) A change in the upstart jobs in the image.

Ted - can you confirm that you had successfully booted the emulator + nexus 4 with the same image using the stock repo version of upstart and only changed upstart when the problem occurred?

I'm testing in the emulator FWIW as do not have real hardware.