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 #995183 reported by Eli Pasetes on 2012-05-05

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

Error message popped up while I launched Terminal from keyboard shortcut. Terminal launched pro7v8K9Mperly but this error message popped up. I re-installed man-db 2.6.1-2 using Synaptics to see if this will resolve this random error.

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
ApportVersion: 2.0.1-0ubuntu7
AptOrdering:
knockd: Install
knockd: Configure
Architecture: i386
Date: Sat May 5 07:18:29 2012
DpkgTerminalLog:
Unpacking knockd (from .../knockd_0.5-3ubuntu1_i386.deb) ...
Processing triggers for man-db ...
debconf: DbDriver "templatedb": /var/cache/debconf/templates.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing man-db (--unpack):
subprocess installed post-installation script returned error exit status 1
DuplicateSignature:
Unpacking knockd (from .../knockd_0.5-3ubuntu1_i386.deb) ...
Processing triggers for man-db ...
debconf: DbDriver "templatedb": /var/cache/debconf/templates.dat is locked by another process: Resource temporarily unavailable
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 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

Eli Pasetes (pasetese) wrote on 2012-05-05:

Dependencies.txt Edit (653 bytes, text/plain; charset="utf-8")
Df.txt Edit (415 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (80.4 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (63.0 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2012-05-05

tags:

removed: need-duplicate-check

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.