[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 SRU for bug #771372 shows that this bug is still a problem in
maverick: the installer diverts initctl when initially bootstrapping the
base system, but for some reason when it comes time to apply any package
updates (such as from -updates or -proposed), initctl is no longer
diverted, which means calling 'start' directly is guaranteed to fail.
There's a bug in debian-installer that this is happening, but we already
know that procps is also buggy and needs fixed, so we should include
that in the SRU.

** Also affects: procps (Ubuntu Maverick)
   Importance: Undecided
       Status: New

** Changed in: procps (Ubuntu Maverick)
       Status: New => In Progress

** Changed in: procps (Ubuntu Maverick)
   Importance: Undecided => High

-- 
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:
  In Progress
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