[Touch-packages] [Bug 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting

This is still stuck in vivid-proposed I have thought any release counts as Fix Released but good to know that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1390726

[Touch-packages] [Bug 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting

After upgrading sysvinit-utils to version 2.88dsf-53.2ubuntu2 the error messages doesn't appear anymore. ** Changed in: sysvinit (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting

This is still stuck in vivid-proposed, but I fixed that now, it should propagate to vivid soon. ** Changed in: sysvinit (Ubuntu) Status: Fix Released = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting

This bug was fixed in the package sysvinit - 2.88dsf-53.2ubuntu2 --- sysvinit (2.88dsf-53.2ubuntu2) vivid; urgency=medium * debian/sysvinit-utils.maintscript: Clean up obsolete /etc/init/startpar-bridge.conf conffile on upgrades. (LP: #1390726) * debian/initscripts.postinst:

[Touch-packages] [Bug 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sysvinit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu.

[Touch-packages] [Bug 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting

I installed 'startpar' and the problem went away; but sysvinit-utils conflicts with startpar, so somehow the sysvinit-utils package isn't providing the right startpar-* scripts. Debian has a newer version so I'm guessing it may need to be synced. ** Changed in: sysvinit (Ubuntu) Importance:

[Touch-packages] [Bug 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting

Indeed, thanks for spotting. This is an obsolete conffile, and needs to be cleaned up on upgrade. DON'T install startpar! It's broken in Ubuntu (or more specifically, with upstart), I'm going to remove it from vivid now. ** Changed in: sysvinit (Ubuntu) Status: Confirmed = In Progress **

[Touch-packages] [Bug 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting

** Changed in: sysvinit (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1390726 Title: Error message init:

[Touch-packages] [Bug 1390726] Re: Error message init: startpar-bridge (*) main process (*) terminated with status 127 appears multiple times on booting

I have noticed that /var/log/upstart contains many logs for these entries and they all seem to contain /bin/sh: 1: exec: startpar- upstart-inject: not found. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu.