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 #800581 reported by Mohd Faredzuan Bin Abdullah on 2011-06-22

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 dont cause im newbie in ubuntu programe

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: man-db 2.5.9-4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
AptOrdering:
execstack: Install
prelink: Install
execstack: Configure
prelink: Configure
Architecture: i386
Date: Wed Jun 22 17:21:56 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

Mohd Faredzuan Bin Abdullah (faredz9798) wrote on 2011-06-22:

Dependencies.txt Edit (780 bytes, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (52.6 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (456 bytes, text/plain; charset="utf-8")

Revision history for this message

Monkey (monkey-libre) wrote on 2011-06-22:

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. Feel free to continue to report any other bugs you may find.