Ubuntu
man-db package

package man-db 2.5.9-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #868827 reported by smssms on 2011-10-06

This bug report is a duplicate of: Bug #349469: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	man-db (Ubuntu)	New	Undecided	Unassigned

Bug Description

I have no idea, just got this error on start-up.

Been playing with Xfce and Gnome, so assume I have cocked up somewhere...

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: man-db 2.5.9-4
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
Architecture: i386
Date: Tue Oct 4 22:08:57 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: man-db
Title: package man-db 2.5.9-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

smssms (skippsav) wrote on 2011-10-06:

AptOrdering.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (782 bytes, text/plain; charset="utf-8")
Df.txt Edit (505 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (123.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-10-27:

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 349469, 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.