Ubuntu
dpkg package

package libelf1 0.147-2 failed to install/upgrade: ErrorMessage: package libelf1 is already installed and configured

Bug #1014740 reported by chris giblin on 2012-06-18

This bug report is a duplicate of: Bug #541595: [Master] package failed to install/upgrade: package is already installed and configured. Edit Remove

This bug affects 1 person

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

Bug Description

just installed unbuntu and down loaded the latest version

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: libelf1 0.147-2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Jun 18 19:20:04 2012
ErrorMessage: ErrorMessage: package libelf1 is already installed and configured
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: dpkg
Title: package libelf1 0.147-2 failed to install/upgrade: ErrorMessage: package libelf1 is already installed and configured

Tags:

Revision history for this message

chris giblin (chrisgiblin57) wrote on 2012-06-18:

Dependencies.txt Edit (579 bytes, text/plain; charset="utf-8")
VarLogDistupgradeAptlog.gz Edit (5.8 KiB, application/x-gzip)
VarLogDistupgradeApttermlog.gz Edit (42.5 KiB, application/x-gzip)
VarLogDistupgradeHistorylog.gz Edit (17.5 KiB, application/x-gzip)
VarLogDistupgradeLspcitxt.gz Edit (700 bytes, application/x-gzip)
VarLogDistupgradeMainlog.gz Edit (12.0 KiB, application/x-gzip)
VarLogDistupgradeTermlog.gz Edit (36.1 KiB, application/x-gzip)

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-06-18:

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