package man-db 2.6.5-2 failed to install/upgrade: error writing to '<standard output>': Input/output error

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

Bug Description

While attempting to upgrade to 13.10, system crashed and would not boot. Ran repair, and was able to boot. The error message occurred during the first boot after repair.

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: man-db 2.6.5-2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
Date: Thu Oct 17 22:09:03 2013
DuplicateSignature: package:man-db:2.6.5-2:error writing to '<standard output>': Input/output error
ErrorMessage: error writing to '<standard output>': Input/output error
InstallationDate: Installed on 2013-01-08 (282 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
MarkForUpload: True
SourcePackage: man-db
Title: package man-db 2.6.5-2 failed to install/upgrade: error writing to '<standard output>': Input/output error
UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago)

Revision history for this message
Alex Goertzen (alexgoertzen) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1241319, so 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.

tags: removed: need-duplicate-check
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.