Comment 1 for bug 807293

This behavior occurs in both natty upstart package and 1.3 built from source. (DBus access rules taken from 1.3 in both cases)

$ cat $HOME/.init/testjob.conf
#### the test job ####
description "Crashes your system"

task

script
end script
#### end test job

$ initctl --system start testjob
initctl: Message did not receive a reply (timeout by message bus)

Init crashes only if the job executes any command or has "script - end script", even if it's empty.

Jobs starting on signals and with dbus-send like that also crash init.
$ dbus-send --system --print-reply --dest=com.ubuntu.Upstart /com/ubuntu/Upstart/jobs/1000/testjob com.ubuntu.Upstart0_6.Job.Stop array:string: boolean:true

Abstract jobs which do nothing (do not contain exec or script statements) start and stop as they should. Starting on manually emitted signals also work with those jobs.