[Bug 602896] Re: Fails to update in pbuilder: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

[Steve Langasek]

The real bug here is that procps is calling 'start' from the maintainer
script at all.  'start' is not a standardized maintainer script
interface; we should be calling 'invoke-rc.d' instead for all services,
including those with upstart jobs.  If this were fixed, I believe
pbuilder uses an appropriate policy-rc.d in its chroots to avoid
accidentally starting services.

-- 
Fails to update in pbuilder: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
https://bugs.launchpad.net/bugs/602896
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “procps” package in Ubuntu: Confirmed

Bug description:
Binary package hint: procps

# dpkg --configure -a
Setting up procps (1:3.2.8-9ubuntu3) ...
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
dpkg: error processing procps (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 procps

Cause is not allowing propc start to fail in the postinst script. Patch attached.