package man-db 2.6.5-2 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました

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

Bug Description

when upgrade 13.10 to 14.04

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: man-db 2.6.5-2
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Sun May 25 16:34:15 2014
DpkgTerminalLog: Log started: 2014-05-25 16:34:06
ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
InstallationDate: Installed on 2013-06-20 (339 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: man-db
Title: package man-db 2.6.5-2 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
UpgradeStatus: Upgraded to saucy on 2014-05-25 (0 days ago)

Revision history for this message
Tatsuo Indou (indou-tsystem) wrote :
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.