package php-doc (not installed) failed to install/upgrade: subprocess dpkg-deb --fsys-tarfile returned error exit status 2

[Hanmant]

Binary package hint: php-doc

let make ubuntu a awesome OS.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: php-doc (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Tue Jun 14 19:49:25 2011
DpkgTerminalLog:
 Unpacking php-doc (from .../php-doc_20100521-2_all.deb) ...
 dpkg-deb (subprocess): data: internal gzip read error: '<fd:0>: data error'
 dpkg-deb: error: subprocess <decompress> returned error exit status 2
 dpkg: error processing /var/cache/apt/archives/php-doc_20100521-2_all.deb (--unpack):
  subprocess dpkg-deb --fsys-tarfile returned error exit status 2
ErrorMessage: subprocess dpkg-deb --fsys-tarfile returned error exit status 2
SourcePackage: php-doc
Title: package php-doc (not installed) failed to install/upgrade: subprocess dpkg-deb --fsys-tarfile returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

[Steve Beattie (sbeattie)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again. This will likely resolve your issue, but the failure can be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. If this does resolve your bug please set its status to Invalid. Thanks in advance!

[Lior Kaplan (kaplan)]

According to the dmesg log, the / FS became read only. In that case, I would expect the decompress problem to fail writing to the FS. Closing as invalid, as this isn't a problem in the package.