Ubuntu
dpkg package

buntu3 failed to install/upgrade: ErrorMessage: package openjdk-7-jre-headless is already installed and configuredpackage openjdk-7-jre-headless 7~u3-2.1.1~pre1-1u

Bug #1051853 reported by Mike Blyth on 2012-09-17

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

Don't know if it's a bug or misconfiguration, but the system suggested reporting it as one. It appears to have left the system in an unstable state.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: openjdk-7-jre-headless 7~u3-2.1.1~pre1-1ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
Uname: Linux 3.2.0-29-generic-pae i686
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
Date: Mon Sep 17 09:27:00 2012
ErrorMessage: ErrorMessage: package openjdk-7-jre-headless is already installed and configured
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
SourcePackage: dpkg
Title: package openjdk-7-jre-headless 7~u3-2.1.1~pre1-1ubuntu3 failed to install/upgrade: ErrorMessage: package openjdk-7-jre-headless is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Mike Blyth (mjblyth) wrote on 2012-09-17:

Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
VarLogDistupgradeAptlog.gz Edit (406 bytes, application/x-gzip)
VarLogDistupgradeApttermlog.gz Edit (1.1 KiB, application/x-gzip)
VarLogDistupgradeHistorylog.gz Edit (925 bytes, application/x-gzip)

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-09-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.