This problem is caused when upstart attempts to exec directly a command that does not exist
I've created an updated package (upstart version '1.4-0ubuntu5~jh ') in my 'ppa:jamesodhunt/upstart-job-logging' PPA [1] that fixes this issue. Please could those affected by this problem try it out and provide feedback. [1] - https://launchpad.net/~jamesodhunt/+archive/upstart-job-logging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922754 Title: booting without --no-log causes init and plymouth-upstart-bridge to spin at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/922754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
