Ubuntu
bash-completion package

package bash-completion 1:1.2-3ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

Asked by The Compiler

Binary package hint: bash-completion

Probably related to #688991, happened at about the same time, when trying to install a .deb with software centre.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: bash-completion 1:1.2-3ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-2.29-generic 2.6.38-rc3
Uname: Linux 2.6.38-2-generic x86_64
Architecture: amd64
Date: Sun Feb 6 22:58:10 2011
EcryptfsInUse: Yes
ErrorMessage: subprocess installed post-installation script returned error exit status 127
PackageArchitecture: all
SourcePackage: bash-completion
Title: package bash-completion 1:1.2-3ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu bash-completion Edit question
Assignee:
No assignee Edit question
Solved by:
The Compiler
Solved:
Last query:
Last reply:

This question was originally filed as bug #715448.

Revision history for this message
The Compiler (florianbruh-deactivatedaccount) said : 		#1
Revision history for this message
Xavier Bassery (xaba) said : 		#2

I converted your bug report to a question for the time being, because it looks like your system is seriously broken and the issue is not directly related to bash_completion.
Your DpkgTerminalLog.txt file shows that several times during the upgrade, the command awk was not found.
This is quite a serious issue, because awk is a commonly used tool.
In Ubuntu, awk is provided by the package mawk which is a dependency of ubuntu-minimal.
Could you please check whether those two are properly installed on your system?
You could type for instance in a terminal the following:
  dpkg --status mawk ubuntu-minimal

Revision history for this message
The Compiler (florianbruh-deactivatedaccount) said : 		#3

This is weird. Awk is (and probably also was at this time) properly installed.
This never happened again to me though.