Ubuntu
man-db package

package man-db 2.5.7-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #965580 reported by Stephen Cook on 2012-03-26

This bug report is a duplicate of: Bug #1372673: excessive debconf use when triggered. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	man-db (Ubuntu)	New	Undecided	Unassigned

Bug Description

Trying to install Ubuntu 10.04 from flash drive for the first time. Cant seem to get past the 'keyboard' section, obviously i'm a total neubuntu!

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: man-db 2.5.7-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
Uname: Linux 2.6.32-38-generic i686
Architecture: i386
Date: Mon Mar 26 18:02:58 2012
ErrorMessage: subprocess installed post-installation script returned error exit status 1
LiveMediaBuild: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2)
SourcePackage: man-db
Title: package man-db 2.5.7-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

Stephen Cook (stevecook) wrote on 2012-03-26:

AptOrdering.txt Edit (339 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (812 bytes, text/plain; charset="utf-8")
Df.txt Edit (636 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (41.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (368 bytes, text/plain; charset="utf-8")

Ubuntu Foundations Team Bug Bot (crichton) on 2012-03-26

affects:

ubuntu → man-db (Ubuntu)

Revision history for this message

Colin Watson (cjwatson) wrote on 2014-09-23:

Thanks for your report. The basic problem here is that man-db's trigger uses debconf to decide whether to update the manual page database, but debconf is not always reliably usable in triggers. I finally figured out a simple way to avoid this problem, which I'm tracking as bug 1372673. If you are still affected by this locally (which I realise is unlikely in the case of some of the older bugs of this type), then running "sudo dpkg --configure -a && sudo apt-get -f install" in a terminal should normally be enough to get the package management system back to a sensible state.