Ubuntu
man-db package

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

Bug #827982 reported by Rizky Akbar on 2011-08-17

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

Please correct this problem.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: man-db 2.5.9-4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed Aug 17 12:03:06 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: man-db
Title: package man-db 2.5.9-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Rizky Akbar (rayq09) wrote on 2011-08-17:

Dependencies.txt Edit (765 bytes, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Marc Deslauriers (mdeslaur) wrote on 2011-08-24: Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability:	yes → no
visibility:	private → public

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.