package amsn 0.98.3-0ubuntu1 failed to install/upgrade: ErrorMessage: package amsn is already installed and configured

Bug #697813 reported by Marcos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: dpkg

The error about having this package already installed was the second error that appeared during the distribution upgrade. The first error was:

"Could not install 'var/cache/apt/archives/amsn_0.98.3-2ubuntu1_386i.deb' package may not be in a working state. Please consider submitting a bug report about it."

The output was:

corrupted filesystem tarfile - corrupted package archive

Due to the errors above, I'm submitting this bug report.

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: amsn 0.98.3-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic-pae 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic-pae i686
Architecture: i386
Date: Wed Jan 5 10:16:05 2011
ErrorMessage: ErrorMessage: package amsn is already installed and configured
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: dpkg
Title: package amsn 0.98.3-0ubuntu1 failed to install/upgrade: ErrorMessage: package amsn is already installed and configured

Revision history for this message
Marcos (marcos-elias) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

Here is the error:

Unpacking replacement rss-glx ...
dpkg-deb (subprocess): data: internal gzip read error: '<fd:0>: data error'
dpkg-deb: subprocess <decompress> returned error exit status 2
dpkg: error processing /var/cache/apt/archives/rss-glx_0.9.1-3ubuntu1_i386.deb (--unpack):
 subprocess dpkg-deb --fsys-tarfile returned error exit status 2

This looks like memory corruption or disk corruption, could you please run a memory test?

Revision history for this message
Brian Murray (brian-murray) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.