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

[Liviu Andronic]

On Fri, Sep 7, 2012 at 2:21 PM, Stefano Rivera <launchpad at rivera.za.net> wrote:
> Liviu: While chrooted, you probably don't want to start any services.
>
> I suggest creating an executable "/usr/sbin/policy-rc.d" containing
> simply "exit 101". That will make invoke-rc.d refuse to start or stop
> services. Remove this again before trying to boot the system.
>
This is excellent advice! Thank you so much. With the suggestion above
apt-get managed to finish installing the packages.

I still have trouble properly booting the new system, but this is
unrelated to this report.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/602896

Title:
  Fails to update in pbuilder: start: Unable to connect to Upstart:
  Failed to connect to socket /com/ubuntu/upstart: Connection refused

Status in “procps” package in Ubuntu:
  Fix Released
Status in “procps” source package in Maverick:
  Invalid
Status in “procps” source package in Natty:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/602896/+subscriptions