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

Bug #930027 reported by NamelessOne
This bug report is a duplicate of:  Bug #1372673: excessive debconf use when triggered. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
man-db (Ubuntu)
New
Undecided
Unassigned

Bug Description

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

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: man-db 2.6.0.2-3
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 10 11:56:56 2012
DuplicateSignature:
 Unpacking replacement libc-bin ...
 Processing triggers for man-db ...
 debconf: DbDriver "config": could not open /var/cache/debconf/config.dat
 dpkg: error processing man-db (--unpack):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
SourcePackage: man-db
Title: package man-db 2.6.0.2-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to precise on 2012-02-09 (0 days ago)

Revision history for this message
NamelessOne (frure-8) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Colin Watson (cjwatson) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.