package rpcbind 0.2.1-2ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

The specific error message in the logs is:

Preparing to unpack .../rpcbind_0.2.1-2ubuntu2.2_amd64.deb ...
stop: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
invoke-rc.d: initscript rpcbind, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: ... it looks like that went OK
Unpacking rpcbind (0.2.1-2ubuntu2.2) over (0.2.1-2ubuntu2.1) ...
[...]
Setting up rpcbind (0.2.1-2ubuntu2.2) ...
start: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
invoke-rc.d: initscript rpcbind, action "start" failed.

Your bug report says that you are running Ubuntu 14.04, however these error messages indicate you are not running upstart as your init system. Are you running Ubuntu in a chroot on a non-upstart system? If so you should have a policy-rc.d in place to disable starting of services in the chroot. Have you done something to cause an init system other than upstart to be used on Ubuntu 14.04? If so that is entirely unsupported.

Same happened to me during an update of 14.04.

My Ubuntu 14.04 was pretty much genuine (unchanged), after several months of inactivity the update today wanted to install 900MB. When installing rpcbind, it barfed and the crash reporter took me here.

[Expired for rpcbind (Ubuntu) because there has been no activity for 60 days.]