Fails to update in pbuilder: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Bug #602896 reported by
Stefano Rivera
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
procps (Ubuntu) |
Fix Released
|
Low
|
Kees Cook | ||
Maverick |
Invalid
|
High
|
Unassigned | ||
Natty |
Fix Released
|
Low
|
Kees Cook |
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/
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.
Related branches
Changed in procps (Ubuntu): | |
status: | New → Confirmed |
Changed in procps (Ubuntu): | |
status: | Confirmed → Incomplete |
Changed in procps (Ubuntu): | |
assignee: | nobody → Kees Cook (kees) |
milestone: | none → natty-alpha-2 |
Changed in procps (Ubuntu Natty): | |
status: | Confirmed → Fix Committed |
To post a comment you must log in.
Yeah, developing/testing with pbuilder is pretty much impossible because of this bug.
I put the patch into debdiff format if that makes it easier to sponsor.