Ubuntu
logcheck package

package logcheck 1.3.13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #791782 reported by Phil Scott on 2011-06-02

This bug report is a duplicate of: Bug #523896: useradd: cannot lock /etc/passwd; try again later.. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	logcheck (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: logcheck

Haven't a clue. Can barely use command line, let alone understand errors. The system brought me here, it's not my fault! :)

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: logcheck 1.3.13
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Thu Jun 2 11:24:59 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
PackageArchitecture: all
SourcePackage: logcheck
Title: package logcheck 1.3.13 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

Phil Scott (phil-scott) wrote on 2011-06-02:

AptOrdering.txt Edit (435 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (37.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-07-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 523896, 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.