Ubuntu
man-db package

package man-db 2.5.9-4 failed to install/upgrade: подпроцесс установлен сценарий post-installation был завершён по сигналу (Обрыв канала)

Bug #864445 reported by Intervision on 2011-10-02

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

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: man-db 2.5.9-4
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
NonfreeKernelModules: nvidia
AptOrdering:
rawstudio: Install
rawstudio: Configure
Architecture: i386
Date: Sun Oct 2 07:18:24 2011
ErrorMessage: подпроцесс установлен сценарий post-installation был завершён по сигналу (Обрыв канала)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: man-db
Title: package man-db 2.5.9-4 failed to install/upgrade: подпроцесс установлен сценарий post-installation был завершён по сигналу (Обрыв канала)
UpgradeStatus: Upgraded to natty on 2011-05-05 (149 days ago)

Tags:

Revision history for this message

Intervision (ads-net) wrote on 2011-10-02:

Dependencies.txt Edit (782 bytes, text/plain; charset="utf-8")
Df.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (72.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.9 KiB, text/plain; charset="utf-8")

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.