Ubuntu
man-db package

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

Bug #998382 reported by Delplace Vivian on 2012-05-12

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

This bug affects 2 people

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

Bug Description

I was on my Gnome Desktop when it's arrived... I was just doing nothing...

It's maybe because I don't have any space on my '/' partition...

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: man-db 2.6.1-2
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Sat May 12 11:07:19 2012
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
SourcePackage: man-db
Title: package man-db 2.6.1-2 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

Delplace Vivian (delplace-vivian) wrote on 2012-05-12:

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

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-10-30:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in man-db (Ubuntu):
status:	New → Confirmed

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.