Receiving error for /var/cache/apt/archives/fonts-noto-cjk compressed data is corrupt
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apt (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
??
Description: Ubuntu 21.04
Release: 21.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
???-OMEN:~$ apt-cache policy fonts-noto-cjk
fonts-
Installed: 1:20190410+
Candidate: 1:20201206-
Version table:
500 http://
500 http://
*** 1:20190410+
100 /var/lib/
??
fonts-
Installed: 20200323-1build1
Candidate: 20201225-1build1
Version table:
500 http://
500 http://
*** 20200323-1build1 100
100 /var/lib/
3) What you expected to happen
I went to execute the upgrade from Ubuntu 21.03 to 21.04 and now cosistently receiving this error.
4) What happened instead
Continually reciving this error whenever I run Software Update or APT UPGRADE
???@???-OMEN:~$ sudo apt upgrade -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
fonts-noto-cjk fonts-noto-extra
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/128 MB of archives.
After this operation, 11.3 MB of additional disk space will be used.
(Reading database ... 235767 files and directories currently installed.)
Preparing to unpack .../fonts-
Unpacking fonts-noto-cjk (1:20201206-
...
dpkg-deb (subprocess): decompressing archive '/var/cache/
-cjk_1%
error: compressed data is corrupt
dpkg-deb: error: <decompress> subprocess returned error exit status 2
dpkg: error processing archive /var/cache/
06-cjk+
cannot copy extracted data for './usr/
ld.ttc' to '/usr/share/
pected end of file or stream
Preparing to unpack .../fonts-
Unpacking fonts-noto-extra (20201225-1build1) over (20200323-1build1) ...
dpkg-deb (subprocess): decompressing archive '/var/cache/
-extra_
compressed data is corrupt
dpkg-deb: error: <decompress> subprocess returned error exit status 2
dpkg: error processing archive /var/cache/
-1build1_all.deb (--unpack):
cannot copy extracted data for './usr/
an-ExtraCondens
aCondensed.
Errors were encountered while processing:
/var/cache/
/var/cache/
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: apt 2.2.3
ProcVersionSign
Uname: Linux 5.11.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Fri May 14 11:11:23 2021
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: Upgraded to hirsute on 2021-05-14 (0 days ago)
| Trejkaz (trejkaz) wrote | #2 |
Same issue, different Ubuntu version, different archive.
Release: 18.04
apt:
Installed: 1.6.14
My error:
```
Unpacking libpython3.
dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt
dpkg-deb: error: <decompress> subprocess returned error exit status 2
dpkg: error processing archive /tmp/apt-
cannot copy extracted data for './usr/
```
I diagnosed the issue as best I could:
- apt caches files in /var/cache/
- I found the file libpython3.
- On deleting this file, running the command again worked.
Therefore the bug in my case was clearly:
- apt downloaded a corrupt file
- apt did not verify that the file's checksum was correct
- apt proceeded to cache the file despite the checksum being incorrect
- the cached file is now on my system and apt refuses to redownload it
- therefore it is impossible to get it to work without user intervention, in this case by manually deleting the cached file
Suggested fix:
- verify that file checksums are correct BEFORE inserting the file into the cache
- if that is for some reason impossible (for instance if apt does not checksum files - which seems completely ludicrous to me from a security standpoint but I insert it here just in case), at least verify that the archive can be opened, before inserting into the cache
- ideally, if a file found in the cache cannot be uncompressed, delete it from the cache and fetch it again.