Mint 20.3 - (I know, why you no on latest) Firefox failing to update this week- “Compressed data is corrupt”
Any tips/tricks I should know? Edit: formatting is bad with the copy/pasted output. Sorry.
(Reading database … 1048865 files and directories currently installed.) Preparing to unpack …/firefox_116.0.2+linuxmint1+una_amd64.deb … Unpacking firefox (116.0.2+linuxmint1+una) over (116.0+linuxmint1+una) … **dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt
dpkg-deb: error: subprocess returned error exit status 2
dpkg: error processing archive /var/cache/apt/archives/firefox_116.0.2+linuxmint1+una_amd64.deb (–unpack):
cannot copy extracted data for ‘./usr/lib/firefox/fonts/TwemojiMozilla.ttf’ to ‘/usr/lib/firefox/fonts /TwemojiMozilla.ttf.dpkg-new’: unexpected end of file or stream
Preparing to unpack …/mozillavpn_2.16.1-focal1_amd64.deb …
Unpacking mozillavpn (2.16.1-focal1) over (2.15.3-focal1) …
dpkg: warning: unable to delete old directory ‘/usr/lib/mozillavpn’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/lib/mozilla/native-messaging-hosts’: Directory not empty
dpkg: warning: unable to delete old directory ‘/usr/lib/mozilla’: Directory not empty
Errors were encountered while processing:
/var/cache/apt/archives/firefox_116.0.2+linuxmint1+una_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover:** Setting up mozillavpn (2.16.1-focal1) … Installing new version of config file /etc/xdg/autostart/mozillavpn-startup.desktop … Processing triggers for mime-support (3.64ubuntu1) … Processing triggers for hicolor-icon-theme (0.17-2) … Processing triggers for gnome-menus (3.36.0-1ubuntu1) … Processing triggers for dbus (1.12.16-2ubuntu2.3) … Processing triggers for mintsystem (8.5.4) … Processing triggers for desktop-file-utils (0.24+linuxmint1) …
I ran into an issue when I updated Cinnamon to “victoria” release this week. Firefox was removed by the update and I had to manually install it.
That’s pretty odd.
In my case, a
sudo apt clean
wound up doing the trick, but your comment reminded me to come back and post that it’s solved.