package man-db 2.5.7-2 failed to install/upgrade: sous-processus script post-installation installé tué par le signal (Relais brisé (pipe))

Its actually rather unlikely that all the bugs marked as a duplicate of this really are duplicates of this one. This specific bug report was likely due to the segfault found in Dmesg.txt:

  118.870098] software-center[1513]: segfault at ffa6d0d0 ip 0054d0cc sp bfa6d060 error 4 in libcairo.so.2.10800.10[53e000+77000]
[ 142.484522] software-center[1544]: segfault at ffbd9620 ip 008878b9 sp bfbd9600 error 4 in libgobject-2.0.so.0.2400.1[87e000+3d000]
[ 311.409080] software-center[1575]: segfault at 1 ip 011dbf42 sp bf9507ac error 4 in _gtk.so[11cc000+19000]
[ 311.438075] software-center[1576]: segfault at 1 ip 011dbf42 sp bf95088c error 4 in _gtk.so[11cc000+19000]
[ 319.588923] software-center[1592]: segfault at 1 ip 011dbf42 sp bf95170c error 4 in _gtk.so[11cc000+19000]
[ 319.900581] software-center[1603]: segfault at 1 ip 011dbf42 sp bf95170c error 4 in _gtk.so[11cc000+19000]
[ 330.337972] software-center[1659]: segfault at 1 ip 011dbf42 sp bf95170c error 4 in _gtk.so[11cc000+19000]

Sorry for the screw up, I should have been more careful..
Fixed: dupped the ones that refer to the same packages (firefox-gnome-support, chromium l10n, gimp & perl-base), shouldn't those be assigned to their respective packages?

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.