package man-db 2.5.7-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript mit Signal (Broken pipe) getötet

Bug #788802 reported by Heinrich Plies
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

Binary package hint: man-db

Habe Rootpartition und Swap auf 8GB-Usb Stick installiert,/home blieb auf der Festplstte mein Fehler: Ich habe mir nicht die 324 Aktualisierungen reingezogen! statt dessen 2 Appikationen angefordert gruß Bully
l

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: man-db 2.5.7-2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Thu May 26 21:12:57 2011
ErrorMessage: Unterprozess installiertes post-installation-Skript mit Signal (Broken pipe) getötet
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: man-db
Title: package man-db 2.5.7-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript mit Signal (Broken pipe) getötet

Revision history for this message
Heinrich Plies (heinrichplies) wrote :
Revision history for this message
Sérgio Faria (sergio91pt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 617832, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

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.