package linux-image-2.6.32-24-generic 2.6.32-24.41 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
corrupted package during upgrade
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: No
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.32-24-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfebf4000 irq 16'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,
Controls : 13
Simple ctrls : 10
Date: Wed Sep 1 13:35:45 2010
ErrorMessage: corrupted filesystem tarfile - corrupted package archive
Frequency: I don't know.
HibernationDevice: RESUME=
InstallationMedia: Xubuntu 9.10 "Karmic Koala" - Release i386 (20091028.3)
MachineType: ASUSTeK Computer Inc. X51RL
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-
dmi.bios.date: 12/13/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 203
dmi.board.
dmi.board.name: X51RL
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: X51RL
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error caused by a corrupted archive. Please execute the following commands, as it will clear your package cache, in a terminal ( Applications -> Accessories -> Terminal ) :
sudo apt-get clean
sudo apt-get update
Then try performing the update again. This will likely resolve your issue. If so please set the bug's status to Invalid. Thanks in advance!