Comment 1 for bug 1161329

The child-subreaper-failed event may be a red herring: If I remove the code that raises it, init still crashes as described above:

init:com.ubuntu.Upstart.c:2651: Assertion failed in control_emit_event_emitted: env != NULL
Aborted (core dumped)

In fact if I remove all the config files, so that I'm asking Upstart to start up and do nothing, the following is the result:

main: Running with UID 511 as PID 26756 (PPID 8298)
Loading configuration from <home>/test/upstart
Loading configuration from <home>/.init
Loading configuration from /etc/xdg/upstart
Loading configuration from /usr/share/upstart/sessions
control_handle_bus_type: Using session bus
event_new: Pending diaas-start event
Handling diaas-start event
event_finished: Finished diaas-start event
init:com.ubuntu.Upstart.c:2651: Assertion failed in control_emit_event_emitted: env != NULL
Aborted (core dumped)

So this is more like 'upstart doesn't start with --user or --session'