Ubuntu
man-db package

package man-db 2.6.1-1 failed to install/upgrade: installed post-installation script alfolyamat 1 hibakóddal kilépett

Bug #967363 reported by Bitó Tamás on 2012-03-28

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 tried to launch XChatIRC then this error came up.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: man-db 2.6.1-1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Sun Mar 25 14:28:40 2012
ErrorMessage: installed post-installation script alfolyamat 1 hibakóddal kilépett
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111209.1)
SourcePackage: man-db
Title: package man-db 2.6.1-1 failed to install/upgrade: installed post-installation script alfolyamat 1 hibakóddal kilépett
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Bitó Tamás (panzersajt) wrote on 2012-03-28:

AptOrdering.txt Edit (219 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (654 bytes, text/plain; charset="utf-8")
Df.txt Edit (484 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (70.7 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (116.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (73.5 KiB, application/x-gzip)

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-03-29:

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.