Dpkg deb subprocess decompressing archive member lzma error compressed data is corrupt



dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt #324

Comments

stonemandave commented Nov 7, 2021

Selecting previously unselected package octoscreen.
(Reading database . 92001 files and directories currently installed.)
Preparing to unpack octoscreen_2.7.4_armhf.deb .
Unpacking octoscreen (2.7.4-1) .
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 octoscreen_2.7.4_armhf.deb (—install):
cannot copy extracted data for ‘./usr/bin/OctoScreen’ to ‘/usr/bin/OctoScreen.dpkg-new’: unexpected end of file or stream
Errors were encountered while processing:
octoscreen_2.7.4_armhf.deb

I can’t install octoscreen. this is the error i get returned.

The text was updated successfully, but these errors were encountered:

JeffB42 commented Feb 6, 2022

I’m not able to reproduce this. Does this still happen for you?

stonemandave commented Feb 6, 2022

I eventually wiped everything and uploaded a backup and the problem still persisted. I eventually found out it was a plugging causing the problem. Forgot which one. Deleted and problem was solved.

Footer

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Dpkg deb subprocess decompressing archive member lzma error compressed data is corrupt

sudo apt-get update fails to fetch some data:

At the beginning I get this:
*******
Err http://repository.wolfram.com stable Release.gpg
Could not connect to repository.wolfram.com:80 (140.177.204.60). — connect (113: No route to host)
Ign http://repository.wolfram.com stable Release
Err http://repository.wolfram.com stable/non-free armhf Packages
Unable to connect to repository.wolfram.com:http:
Err http://repository.wolfram.com stable/non-free Translation-en_GB
Unable to connect to repository.wolfram.com:http:
Err http://repository.wolfram.com stable/non-free Translation-en
Unable to connect to repository.wolfram.com:http:
********

Then I get this:
*******
Could not connect to raspbian.nh6z.net:80 (198.178.136.37), connection timed out
Fetched 7,804 kB in 2min 0s (64.8 kB/s)
Reading package lists. Done
W: Failed to fetch http://raspbian.nh6z.net/dists/experimental/Release.gpg Could not connect to raspbian.nh6z.net:80 (198.178.136.37), connection timed out

W: Failed to fetch http://repository.wolfram.com/raspbian/ . elease.gpg Could not connect to repository.wolfram.com:80 (140.177.204.60). — connect (113: No route to host)

W: Failed to fetch http://repository.wolfram.com/raspbian/ . f/Packages Unable to connect to repository.wolfram.com:http:

W: Failed to fetch http://repository.wolfram.com/raspbian/ . tion-en_GB Unable to connect to repository.wolfram.com:http:

W: Failed to fetch http://repository.wolfram.com/raspbian/ . slation-en Unable to connect to repository.wolfram.com:http:

W: Some index files failed to download. They have been ignored, or old ones used instead.
*******

If I then try to proceed with:
sudo apt-get upgrade
sudo rpi-update

I eventually end-up getting kicked out of my own system and my login does not get recognized anymore: «Access denied» anytime I try to use a command.

Obviously the error messages state that they cannot connect to the sources that provide the data.
This in turn crashed any attempt to update that I make.
I have tried to contact NH6Z regarding his directory but had no reply.

Is there a way to circumvent this problem or do I have just wait until the data becomes available again?
I am curious as to how my system decides to go to these data sources specifically when i make an update.
I assume that these would have been tested but it looks like I am assuming wrong.
I am also surprised that I am the only person with this problem.

Читайте также:  Collect2 exe error ld returned 5 exit status что это

Any help in solving this problem would be greatly appreciated.

Re: sudo apt-get update fails to fetch data

You are sure you are not hacked ? You haven’t done any port-forwarding of port 22 without changing password or anything ?

Or are you running a very old version of Raspbian ? I cant reach any «repository.wolfram.com» either.
I dont think «raspbian.nh6z.net» is on any official mirror list, I would check my «sources.list» in «/etc/apt/get».

Re: sudo apt-get update fails to fetch data

Start by checking your network. Can you ping Google

ping -c3 8.8.8.8
ping -c3 google.com

Can you ping 198.178.136.37 or raspbian.nh6z.net

ping -c3 198.178.136.37
ping -c3 raspbian.nh6z.net

Because when I try that it’s your Raspbian mirror that’s broken.

When you discover a broken mirror you’ll need to report it to the folks who run your mirror.

https://raspbian.org/RaspbianMirrors has a list of alternatives. You can pick a local mirror and update /etc/apt/sources.list.d/raspi.list to use that address.

Languages using left-hand whitespace for syntax are ridiculous

DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors — are all on my foes list.

The use of crystal balls and mind reading is prohibited.

Re: sudo apt-get update fails to fetch data

Re: sudo apt-get update fails to fetch data

Thank you everybody for your suggestions.

@ topguy: I do not think that I am hacked but again in this modern world. I do use 22 for SSH on the pi but I have not tinkered with anything else. It is possible that I am running a fairly old version of Raspbian. I do not think I have updated for a few months. It seems that the wolfram repository now states «NOT FREE» which is probably why we cannot access it anymore. I am not very familiar with mirror lists, etc. I am going to check this out.

@ dougie: I get the same results as you with the google ok but the nh6z site not responding. I checked the link you provided for mirrors and could not find wolfram nor nh6z. So maybe these are not being supported / updated anymore and are off the list (assuming they were mirros in the first place).

@ DirkS: I think you are correct. OpenDV is not supported anymore and the source data has simply vanished.

In order to get around the problems encountered so far, this is what I have done:
* went into /etc/apt/sources.list.d/
* went into opendv.list and commented out «deb http://raspbian.nh6z.net/ experimental main»
* went into wolfram.list and commented out «deb http://repository.wolfram.com/raspbian/ stable non-free»
* ran apt-get update
Result: 0 errors ! So we are progressing.

I then ran apt-get upgrade and got the following errors:
*******
dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt
dpkg-deb: error: subprocess returned error exit status 2
dpkg: error processing /var/cache/apt/archives/libicu48_4.8.1.1-12+deb7u7_armhf.deb (—unpack):
cannot copy extracted data for ‘./usr/lib/arm-linux-gnueabihf/libicudata.so.48.1.1’ to ‘/usr/lib/arm-linux-gnueabihf/libicudata.so.48.1.1.dpkg-new’: unexpected end of file or stream
*******
and
*******
dpkg-deb (subprocess): decompressing archive member: internal gzip read error: ‘ : invalid code lengths set’
dpkg-deb: error: subprocess returned error exit status 2
dpkg: error processing /var/cache/apt/archives/tzdata_2017c-0+deb7u1_all.deb (—unpack):
corrupted filesystem tarfile — corrupted package archive
Processing triggers for man-db .
Errors were encountered while processing:
/var/cache/apt/archives/libicu48_4.8.1.1-12+deb7u7_armhf.deb
/var/cache/apt/archives/tzdata_2017c-0+deb7u1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
*******

Читайте также:  System exception and business exceptions

After that, I tried to run rpi-update and got:
*******
/usr/bin/rpi-update: line 115: /usr/bin/basename: Permission denied
*******

So, we are making some progress as we are now past the errors in the «apt-get update» phase but am still struggling to get the rest working.

Источник

Fix “Sub-process /usr/bin/dpkg returned an error code (1)” In Ubuntu

Today I tried to upgrade my Ubuntu 20.04 LTS desktop and I encountered with this error — «Sub-process /usr/bin/dpkg returned an error code (1)». It is one of the common issue in Ubuntu and other DEB-based systems.

This error usually happens due to a failed application installation, or if the dpkg package installer becomes corrupted or interrupted in mid-way while installing a package.

Here are the commands that I tried to upgrade my Ubuntu desktop:

And. here is the error message:

Fix «Sub-process /usr/bin/dpkg returned an error code (1)» In Ubuntu

If you encountered with an error like above, worry not! Here, I have given a few workarounds to solve «Sub-process /usr/bin/dpkg returned an error code (1)» issue in Ubuntu and its variants such as Linux Mint, Pop OS.

Solution 1 — Reconfigure dpkg database

If the package installation process is stopped or interrupted in mid-way, the dpkg database might be corrupted. Reconfiguring dpkg database may solve this issue.

To reconfigure dpkg database, simply run:

This command will try to fix the corrupted dpkg database and then reconfigure all broken packages. This command usually fixes the dpkg returned an error code (1) problem. If it didn’t solve the issue for any reason, follow the subsequent solutions.

Solution 2 — Force install the application

If the first method didn’t work, run the following command to perform force install:

Here, -f (or —fix-broken ) option will attempt to correct the Ubuntu system with broken dependencies.

If these two solutions didn’t help and the issue still persists, try the next solution.

Solution 3 — Remove the problematic application .deb file from the local cache folder and reinstall it

As you see in the error message (the last two lines), the eog package is causing this error.

For those wondering, eog (short for Eye of GNOME) is the official and default image viewer for the GNOME desktop environment. So this package is problematic and doesn’t let me to upgrade my Ubuntu.

When you install a package, it will be downloaded and saved in the cache folder /var/cache/apt/archives/ .

To fix this error, remove the cached package using command:

Replace eog_3.36.2-0ubuntu1_amd64.deb with your package.

Clean the package cache folder:

Update the source lists:

Upgrade your system:

Finally, get the fresh package from official repositories and reinstall it like below:

This solution worked for me.

Solution 4 — Remove the problematic application

This should be your last resort. If none of the above methods help, remove the problematic package from your system like below:

This command will remove eog with all its configuration files from the system.

And also find and remove all files associated with the broken package.

To find all files related to a package, run:

Sample output:

Remove them manually.

That’s it. At this stage, any one of the these four solutions should have helped you to fix «Sub-process /usr/bin/dpkg returned an error code (1)» in Ubuntu and other DEB-based systems.

Читайте также:  Error access violation перевод

Solutions to other common problems in Ubuntu:

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[Solved] Problem with Firefox 44 Add-ons. — Update Problem

[Solved] Problem with Firefox 44 Add-ons. — Update Problem

Post by Mazda81 » Wed Feb 03, 2016 4:48 pm

Re: Problem with Firefox 44 Add-ons.

Post by karlchen » Wed Feb 03, 2016 7:28 pm

The screenshot that you posted holds a bunch of error messages displayed by the Mint Update Manager.
Sadly the beginning is missing. Yet, it can be seen that an important cache file is corrupted, /var/lib/dpkg/available.
This corruption seems to have caused a number of failing operations.
As a consequence the update to Firefox 44 must be considered failed.
This, too, is the reason why the Firefox plugins do no longer work.

What you can try is this:

  • Close the window that displays the error messages, in case it should still be open.
  • Close Firefox, in case it should still be open.
  • Close any programme like Update Manager, Software Manager or Synaptic, in case any of them should be open.
  • Launch a terminal window.
  • Inside the terminal window execute the following commandlines. Post the complete screen output of each commandline here, so that it is possible to tell apart success and failure.

Further steps will depend on the result of the posted commandlines.

Regards,
Karl

P.S.:
I will be offline now for the night. So there will be no quick feedback from my side for the next few hours. Sorry.

Re: Problem with Firefox 44 Add-ons.

Post by Mazda81 » Thu Feb 04, 2016 7:52 am

Re: Problem with Firefox 44 Add-ons.

Post by karlchen » Thu Feb 04, 2016 8:29 am

One handling request for the future first:
The screen output from terminal window: please, do not take screenshots from it. It is pure text. Therefore in future, please, mark the commandline and its output and copy it into the clipboard by pressing C. Paste it into the post here by pressing V. And if you are nice, then you enclose the pasted text in [ code ] tags (see button) on top of the forum editor.
Reason:
Screenshots are frequently incomplete, i.e. part of the screen output is missing. Marking, copying and pasting the text from the terminal window will make sure things are complete.
Nothing can be copied and pasted for future use from screenshots. But text can be reused. (Avoids typing errors e.g.)

So far things look as expected.
One question though:
In the second screenshot we see that the commandline «sudo apt-get update» fails with the complaint the command «sudo » (note the trailing blank in the error message) could not be found. But the first screenshot seems to display the lower part of a successful «sudo apt-get update» command.

I suggest to try an reinstall Firefox 44 from the commandline now (terminal window)

Please, post the commandlines and their complete screen output.

Источник

Оцените статью
toolgir.ru
Adblock
detector