package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: ErrorMessage: subprocess dpkg-deb --fsys-tarfile returned error exit status 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkms (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
package nvidia-current 195.36.
ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: nvidia-current 195.36.
ProcVersionSign
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelMo
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 195.36.24 Thu Apr 22 19:10:14 PDT 2010
GCC version: gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
Architecture: amd64
Date: Tue Oct 19 22:19:11 2010
DkmsStatus:
vboxhost, 3.2.10, 2.6.32-25-generic, x86_64: installed
vboxhost, 3.2.10, 2.6.35-22-generic, x86_64: installed
ErrorMessage: ErrorMessage: subprocess dpkg-deb --fsys-tarfile returned error exit status 2
MachineType: Gigabyte Technology Co., Ltd. P55-UD4P
ProcCmdLine: root=UUID=
SourcePackage: nvidia-
Title: package nvidia-current 195.36.
dmi.bios.date: 12/03/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: P55-UD4P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: P55-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.32-25-generic
tags: | added: lucid |
affects: | nvidia-graphics-drivers (Ubuntu) → dkms (Ubuntu) |
ric_2.6. 35-22.35_ amd64.deb) ... 2.6.35. 22.23_amd64. deb) ... apt/archives/ nvidia- current_ 260.19. 06-0ubuntu1_ amd64.deb (--unpack):
Removing all DKMS Modules
Done.
-generic_
Unpacking replacement nvidia-current ...
.0':
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/
subprocess dpkg-deb --fsys-tarfile returned error exit status 2
From those logs this looks like it was from file corruption on the disk and/or an incomplete download. Not much that we can do about either of those.