package libxcb-randr0 1.7-3 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./usr/lib/i386-linux-gnu/libxcb-randr.so.0.1.0'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libxcb (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
i have no idea w/ this
ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: libxcb-randr0 1.7-3
ProcVersionSign
Uname: Linux 3.0.0-10-generic i686
NonfreeKernelMo
Architecture: i386
Date: Sun Sep 4 10:10:45 2011
DistUpgraded: Log time: 2011-09-02 12:58:31.190114
DistroCodename: oneiric
DistroVariant: ubuntu
DuplicateSignature:
Unpacking libxcb-randr0 (from .../libxcb-
dpkg-deb (subprocess): data: internal gzip read error: '<fd:0>: invalid distance too far back'
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg: error processing /var/cache/
short read on buffer copy for backend dpkg-deb during `./usr/
ErrorMessage: short read on buffer copy for backend dpkg-deb during `./usr/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Dell Inc. Inspiron N3010
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: libxcb
Title: package libxcb-randr0 1.7-3 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./usr/
UpgradeStatus: Upgraded to oneiric on 2011-09-03 (3 days ago)
dmi.bios.date: 03/10/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 08FJWT
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron N3010
dmi.product.
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.5.
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
tags: | removed: need-duplicate-check |
Hey rgv151,
Hi, thanks for reporting this issue during the development period of
Ubuntu.
I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?
Are you still able to reproduce the issue? If not, do you think the bug
report can be closed, or do you think we should continue tracking it?