Содержание
- Debian User Forums
- Dpkg error can’t solve
- Dpkg error can’t solve
- Linux Mint Forums
- [SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13
- [SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13
- Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)
- Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)
- Ubuntu Wiki
- DebuggingInstallationIssues
- Introduction
- Known issues
- Corrupted package archive
- Not a Debian format archive
- Corrupted filesystem tarfile
- —fsys-tarfile
- short read — Input/output error
- Exec format error
- triggers ci file contains unknown directive syntax
- lzma : decoder error
- files list file missing final newline / contains empty filename
- Inconsistent state
- Package in bad inconsistent state
- package is already installed and configured
- Other issues
- Can’t access archive
- No space left on device
- DbDriver «config» is locked
- /var/lib/defoma/locked exists
- /etc/defoma/hints/FONTNAME.hints: Unable to open, or empty
- Non-bugs
- Segmentation Fault — Exit status 139
- Other resources
Debian User Forums
Dpkg error can’t solve
Dpkg error can’t solve
#1 Post by theblueplll » 2019-07-04 15:29
Machine is an older machine I was trying to setup for a project running Debian Buster 32bit
AMD Semperon 3000+ 1.5gb ram no desktop(don’t need one for what I want to do)
Seems to run great untill I try to install a package.
I don’t have anything from any repo besides Debians official repos on purpose.
I keep getting this when I try to install things.
Partitions are setup like this
Doesn’t seem to matter what it is although some packages will install without error.
Have tried the instructions at this link and a few similar things to no avail
I also can NOT remove the package once this happens when I try to I get unment dependency warnings.
And if I try to install the dependencies it starts with the dpkg errors all over again.
This started when I had Buster installed on it originally so I switched to Stretch thinking the older hardware would work better but had the same problem.
So i reinstalled Buster again and some stuff was whacky so I looked into it and found out either my iso was corrupted or my flash drive was acting funny.
So I tried with a new usb stick and a fresh download that I verified and check for integrity and it seemed to install a lot faster and smoother.
2 days go by and the problem comes back.
Could this be a hardware problem somehow? Maybe a bad hdd?
Both drives are kind of old.
Any other information that could be needed please just ask and I will do my best to share it.
Источник
Linux Mint Forums
Welcome to the Linux Mint forums!
[SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13
[SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13
Post by LittleScriptMan » Mon Jun 20, 2022 5:36 am
Tried this morning to update apturl package version 0.5.2+linuxmint12 as suggested in Update Manager but got these errors in return
/var/cache/apt/archives/apturl_0.5.2+linuxmint12_all.deb uses an unknown compression process for control.tar.zst
and :
dpkg-deb —control subprocess returned error exit status 2
(which seems to be an unpack error probably caused by the unability to perform decompression of the archive).
Thanks for any help or suggestion.
PS : quick insight of the system (inxi -GS + Repos) — Kernel upgrade was necessary to allow wifi connection which didn’t work with 5.10 serie
Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)
Post by abu » Mon Jun 20, 2022 6:15 am
Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)
Post by karlchen » Mon Jun 20, 2022 6:52 am
Hello, LittleScriptMan. Hello, Abu.
Foreword:
At this point in time I can only crosscheck with LM 19.3, apturl 0.5.2+linuxmint8. LM 19.3 is not LMDE, so my findings may or may not be relevant.
Inner archive format of apturl.deb package
The inner archives in apturl 0.5.2+linuxmint8 is still .xz. No problem reading and extracting .xz archives here.
But on LMDE 4 and LMDE 5 the latest apturl 0.5.2+linuxmint12 has got inner archives of the format .zst.
In order to read .zst archives you seem to need a package simply named zstd.
By default this package is not pre-installed on LM 19.3.
I am not sure whether it will really resolve your problem.
Check whether zstd is available on your LMDE systems. Command: which zstd
In case this comes back empty, you might install zstd from the software repos.
Command: sudo apt-get install zstd
This might be sufficient to enable the Update Manager to read and install the apturl package 0.5.2+linuxmint12.
It is imaginable, however, that Update Manager will not use the commandline tool zstd, but instead some supporting library, which provides .zst archive reading capabilities.
In this case, you will have to wait for advice given by other LMDE users.
Update/Solution:
As explained in Clem’s post further down , the problem has been resolved by publishing a corrected apturl 0.5.2+linuxmint13.
So refresh your list of available software updates. It should display apturl 0.5.2+linuxmint13. The inner archives are in .xz format again. The installation should succeed.
Источник
Ubuntu Wiki
DebuggingInstallationIssues
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.
Introduction
This page lists some general issues that users might encounter while performing updates of their system. Apport will usually detect these failures and file a bug in Launchpad. These bugs can be identified by the bug tag ‘apport-package’ and can occur on nearly any package.
There are usually log file attached to the report which differs depending on the kind of install/upgrade:
Package install/upgrade: DpkgTerminalLog
Distribution upgrade: VarLogDistupgradeMain and VarLogDistupgradeApttermlog
Detailed informations about debugging updatemanager can be found at DebuggingUpdateManager.
Documented below are the most commonly reported issues. For each case there is a description and a sample report and when applicable there is a workaround or fix and the master report it should be marked a duplicate of.
Known issues
Corrupted package archive
These errors indicates a corrupted archive (.deb or files on disk) The root cause of the corruption may be a bad network connection, faulty hardware, hardware shutdown.
For those report the common workaround and stock response is:
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error caused by a corrupted archive. Please execute the following commands, as it will clear your package cache, in a terminal ( Applications -> Accessories -> Terminal ) :
sudo apt-get clean
sudo apt-get update
Then try performing the update again. This will likely resolve your issue. If so please set the bug’s status to Invalid. Thanks in advance!
Not a Debian format archive
This error indicated that the header of the .deb archive is not recognized as a valid debian format.
Corrupted filesystem tarfile
—fsys-tarfile
short read — Input/output error
The ‘short read’ error happens when trying to install a partially downloaded package. The front-end verify the integrity of the archive, but it is not the case if dpkg is invoked directly.
An input/output error is likely to mean filesystem corruption, hardware problems or no space left on hard disk. The typical errors are:
The suggestion is to run a manual fsck and look whether the hard drive or storage device is operating correctly (dmesg may contain helpful information too)
TODO: Write a standard response
Exec format error
This error indicates that the installation or removal script is corrupted. It is caused by a sudden system failure during dpkg operation (power failure, hardware failure, . ) on filesystems supporting delayed allocation (like ext4, xfs, btrfs, . )
Empty files or files filed with garbage are left on the hard drive. The file causing the dpkg error is one of /var/lib/dpkg/info/PACKAGE_NAME.p*
This error can occur either during installation or removal of the package.
During installation of a package
During removal of a package
Workaround A: Finish the install
sudo apt-get clean
sudo aptitude download python-libvirt
sudo dpkg —unpack ./python-libvirt*.deb
sudo dpkg —configure python-libvirt
Workaround B: Remove the package and reinstall
sudo rm /var/lib/dpkg/info/flashplugin-installer.
sudo apt-get remove —purge flashplugin-installer
sudo apt-get clean
sudo apt-get update
Then reinstall the package
Note: Change the package by the one which failed (check the log file)
Note about localized error message:
Finding this error in the log is not always easy because the error string has been localized.
- Erreur de format pour exec()
- Error de formato ejecutable
- Errore di formato di exec
- Exec format error
- Formatfel på körbar fil
- Érvénytelen végrehajtható fájlformátum
- Exec formátum hiba
- Verkeerd uitvoerbaar bestand
- Exec 格式错误
triggers ci file contains unknown directive syntax
This is the same kind of issue than the one above. It means that the trigger file is empty or corrupted. The file is /var/lib/dpkg/info/PACKAGE.triggers This error can occur during installation or removal of a package.
During installation of a package
Workaround
remove the file /var/lib/dpkg/info/PACKAGE.triggers
sudo rm /var/lib/dpkg/info/PACKAGE.triggers
and run
sudo dpkg —purge ureadahead
then clean your cache
sudo apt-get clean
and try performing the install of ureadahead again.
lzma : decoder error
files list file missing final newline / contains empty filename
This error indicates that the file /var/lib/dpkg/info/PACKAGE_NAME.list is corrupted ( empty or full of garbage ) The reason may be a disk error, a memory error, a process being interrupted during unpack, .
Typically these errors take the form :
files list file for package packagename contains empty filename
or
files list file for package packagename is missing final newline
Workaround: Recreate the file list from .deb
This can be fixed, with a little work. If you have the .deb file for the offending package currently available on your system, then check its integrity by running:
dpkg —contents /var/cache/apt/archive/libgnome2-0_2.24.1-0ubuntu3_i386.deb
or get a .deb file by running :
sudo apt-get install —reinstall —download-only libgnome2-0
Once you have a valid .deb file, then you can reconstitute the file. First become root by using sudo -s (enter your administrative user password if necessary), and then use the following command (copy/paste and change the package name accordingly):
Inconsistent state
Package in bad inconsistent state
Workaround A:
Please open a Terminal from the menu Applications->Accessories->Terminal and type or copy and paste the row below:
sudo apt-get —reinstall install cupsys
sudo dpkg —configure -a
sudo apt-get -f install
give your user password when requested, you don’t see nothing when you type it, then press enter.
Workaround B:
Try the command below to purge the offending packages :
sudo dpkg —purge —force-remove-reinstreq flashplugin-installer flashplugin-nonfree
Then to reinstall :
sudo apt-get install flashplugin-installer
package is already installed and configured
Conditions of this failure are unknown. Please provide any additional informations in the master report.
Note to triagers: Before marking a report as duplicate, be sure that there is no other error in the log file term.log . In other words, don’t blindly duplicate because the title says ‘already installed and configured’.
Workaround A:
sudo dpkg —configure -a
Workaround B:
sudo apt-get install —reinstall language-pack-ar
Other issues
Can’t access archive
The source of this error is not clearly identified and needs further investigation (see comment #3 of the master report)
No space left on device
Bug 105113 was a request to detect this prior to performing any updates.
Bug 312491 was a request to report to the user when running out of disk space.
This error is self-explanatory.
Note about localized error message:
Despite the fact that there is no ambiguity regarding the cause of the failure, finding this error in the log is not always easy because the error string has been localized. Checking for the strings —unpack and buffer_write in the error log is a good indication too.
DbDriver «config» is locked
fuser -v will return the locking process if any. Kill it and try performing the upgrade again. Most often, this is only a transient situation and fuser will return nothing. Simply performing the update again should solve this issue.
/var/lib/defoma/locked exists
Under certain circumstances font packages failed to install with the following error:
Workaround
Open a terminal (Applications -> Accessories -> Terminal ) and run the following command:
/etc/defoma/hints/FONTNAME.hints: Unable to open, or empty
Under certain circumstances font packages failed to install with the following error:
This is due to a corrupted hint file.
Workaround
To workaround it, open a terminal and run the following commands:
Then try performing the install again. Replace the font file name (FONTNAME) by the font name failing on your system (e.g ttf-dejavu-extra, ttf-konatu, . )
Non-bugs
Common issues arising from hardware failures, common invalid bugs for this category.
Segmentation Fault — Exit status 139
If the installation failed with no reason with an exit status 139, that the configuration script is trivial and there is no other report of this kind for that package, then this is very likely a memory corruption error.
The error from the term.log will show something like this:
There is not much we can do except the advice below:
Thanks for your report.
This looks like a hardware issue. Could you run memtest on your system? (boot a live CD / USB key and select test memory)
The reporter will most of the time says that the test reports error. If so, then close the report.
Note : an exit status 139 can also appear on other scenarios that aren’t related to faulty memory modules. For example, if you install a Hardy guest on a Lenny host using Xen, and then try an apt-get upgrade on the Hardy guest, that will fail with a segfault and an exit status 139 if you forget to disable /lib/tls as advised in the Xen Faq
Other resources
- Add note about localized messages in log file and method to process those reports
- Search for master reports, complete missing references in wiki and cross-reference report/wiki content
Add section ‘How to triage’ and merge the one from DebuggingUpdateManager
Add missing descriptions & workaround
DebuggingInstallationIssues (последним исправлял пользователь mail 2014-11-17 18:12:57)
The material on this wiki is available under a free license, see Copyright / License for details.
Источник
I just upgraded to the 10.10 RC earlier and had a few problems with graphic drivers (x didnt start) But i have remedied that now.
When i run ‘sudo apt-get install -f’ i get this:
will@UbuntuBox:/mnt/slax$ sudo apt-get install -f
[sudo] password for will:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
libmono-wcf3.0-cil openoffice.org-calc openoffice.org-core
The following NEW packages will be installed:
libmono-wcf3.0-cil
The following packages will be upgraded:
openoffice.org-calc openoffice.org-core
2 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
16 not fully installed or removed.
Need to get 0B/32.5MB of archives.
After this operation, 1,929kB disk space will be freed.
Do you want to continue [Y/n]? Y
(Reading database ... 201565 files and directories currently installed.)
Preparing to replace openoffice.org-calc 1:3.2.1-6ubuntu2~10.04.1 (using .../openoffice.org-calc_1%3a3.2.1-7ubuntu1_i386.deb) ...
Unpacking replacement openoffice.org-calc ...
xz: (stdin): Compressed data is corrupt
dpkg-deb: subprocess <decompress> returned error exit status 1
dpkg: error processing /var/cache/apt/archives/openoffice.org-calc_1%3a3.2.1-7ubuntu1_i386.deb (--unpack):
short read on buffer copy for backend dpkg-deb during `./usr/lib/openoffice/basis3.2/program/libscfiltli.so'
dpkg: regarding .../openoffice.org-core_1%3a3.2.1-7ubuntu1_i386.deb containing openoffice.org-core:
openoffice.org-core conflicts with openoffice.org-calc (<< 1:3.2.1-7ubuntu1)
openoffice.org-calc (version 1:3.2.1-6ubuntu2~10.04.1) is present and installed.
dpkg: error processing /var/cache/apt/archives/openoffice.org-core_1%3a3.2.1-7ubuntu1_i386.deb (--unpack):
conflicting packages - not installing openoffice.org-core
Unpacking libmono-wcf3.0-cil (from .../libmono-wcf3.0-cil_2.6.7-3ubuntu1_all.deb) ...
dpkg-deb (subprocess): data: internal gzip read error: '<fd:0>: data error'
dpkg-deb: subprocess <decompress> returned error exit status 2
dpkg: error processing /var/cache/apt/archives/libmono-wcf3.0-cil_2.6.7-3ubuntu1_all.deb (--unpack):
subprocess dpkg-deb --fsys-tarfile returned error exit status 2
Errors were encountered while processing:
/var/cache/apt/archives/openoffice.org-calc_1%3a3.2.1-7ubuntu1_i386.deb
/var/cache/apt/archives/openoffice.org-core_1%3a3.2.1-7ubuntu1_i386.deb
/var/cache/apt/archives/libmono-wcf3.0-cil_2.6.7-3ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Any idea how i can get the broken packages fixed?
Cheers,
Will
asked Oct 3, 2010 at 19:03
This line is a clue:
xz: (stdin): Compressed data is corrupt
Perhaps something happened to the .deb during transfer. Execute a sudo apt-get clean and then try again to force it to redownload the debs.
There are similar reports in Launchpad on these kind of errors for OpenOffice lately. This is likely a bug and should be reported as such.
answered Oct 3, 2010 at 19:24
Jorge CastroJorge Castro
70k123 gold badges462 silver badges652 bronze badges
1
-
theblueplll
- Posts: 154
- Joined: 2019-04-29 01:17
- Been thanked: 2 times
Dpkg error can’t solve
#1
Post
by theblueplll » 2019-07-04 15:29
Machine is an older machine I was trying to setup for a project running Debian Buster 32bit
AMD Semperon 3000+ 1.5gb ram no desktop(don’t need one for what I want to do)
Seems to run great untill I try to install a package.
I don’t have anything from any repo besides Debians official repos on purpose.
I keep getting this when I try to install things.
Partitions are setup like this
Code: Select all
60gb hd
/boot
/root
and /swap
other drive is 40gb where my /home partition is
Code: Select all
dpkg-deb: error: <decompress> subprocess returned error exit status 2
dpkg: error processing archive /var/cache/apt/archives[package name here].deb (--unpack):
dpkg=deb --fsys-tarfile subprocess returned error exit status 2
Errors were encountered while prrocessing:
/var/cache/apt/[package name here].deb
Error Sub-process /usr/bin/dpkg returned error code (1)
Doesn’t seem to matter what it is although some packages will install without error.
Have tried the instructions at this link and a few similar things to no avail
Code: Select all
https://itsfoss.com/dpkg-returned-an-error-code-1/
I also can NOT remove the package once this happens when I try to I get unment dependency warnings.
And if I try to install the dependencies it starts with the dpkg errors all over again.
This started when I had Buster installed on it originally so I switched to Stretch thinking the older hardware would work better but had the same problem.
So i reinstalled Buster again and some stuff was whacky so I looked into it and found out either my iso was corrupted or my flash drive was acting funny.
So I tried with a new usb stick and a fresh download that I verified and check for integrity and it seemed to install a lot faster and smoother.
2 days go by and the problem comes back.
Could this be a hardware problem somehow? Maybe a bad hdd?
Both drives are kind of old.
Any other information that could be needed please just ask and I will do my best to share it.
-
GarryRicketson
- Posts: 5871
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: Dpkg error can’t solve
#2
Post
by GarryRicketson » 2019-07-04 15:57
Please show how you are running ‘dpkg’ ? IE:normal user, sudo, su, su — ,….etc
You show the output from when you run the command, but please show everything, including how you run the command.
For example:
Code: Select all
garry@debian:~$ dpkg conky-all_1.10.8-1+b1_amd64.deb
dpkg: error: need an action option
Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;
Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
Doesn’t seem to matter what it is although some packages will install without error.
Don’t you think that the actual package name, and perhaps where you got it might be relevant ? Especially since «some packages» will install with out error. Maybe the mystery package is not packaged properly.
Could this be a hardware problem somehow? Maybe a bad hdd?
Both drives are kind of old.
Could be, if you suspect that it is, then the logical thing to do is to use a live device , with some drive testing tools, and test it. I can not do that for you, since I am not there, and can not access your, you need to do that your self, or take it to someone that can do it for you.
===== also===
You claim you are only using Debian repos, is there some reason you don’t just use :
Use ‘apt’ or ‘aptitude’ for user-friendly package management;
?
-
theblueplll
- Posts: 154
- Joined: 2019-04-29 01:17
- Been thanked: 2 times
Re: Dpkg error can’t solve
#3
Post
by theblueplll » 2019-07-04 16:22
Doesn’t seem to matter what it is although some packages will install without error.
Don’t you think that the actual package name, and perhaps where you got it might be relevant ? Especially since «some packages» will install with out error. Maybe the mystery package is not packaged properly.
Could this be a hardware problem somehow? Maybe a bad hdd?
Both drives are kind of old.Could be, if you suspect that it is, then the logical thing to do is to use a live device , with some drive testing tools, and test it. I can not do that for you, since I am not there, and can not access your, you need to do that your self, or take it to someone that can do it for you.
===== also===
You claim you are only using Debian repos, is there some reason you don’t just use :Use ‘apt’ or ‘aptitude’ for user-friendly package management;
apt install XXX is how I install things what I meant was that only the official repos are in my sources.list sorry if that was confusing or not clear enough.
Doesn’t seem to make a difference if I log my normal user and use sudo or sudo su or if I log the root account when this is happening.
It will get part of the way into installing and gie me the dpkg error.
If I try to uninstall it I get the unmet dependency error and if I try to install dependencies I get the dpkg error all over again.
For instance this is happening with android sdk which I wanted for the adb tools.
But like I said didn’t seem to matter what package it would randomly decide to do this to me.
As far as testing the dries from a live cd that is no problem i know how to do it for the most part LoL
Is there some tool besides maybe fsck that you would reccomend to use?
Sorry if I am not being clear enough it is not intentional.
-
Deb-fan
- Posts: 1047
- Joined: 2012-08-14 12:27
- Been thanked: 4 times
Re: Dpkg error can’t solve
#4
Post
by Deb-fan » 2019-07-04 17:22
Automagically resolving/installing dependencies is what apt/itude are for and don’t need a Desktop/WM to use them. Have had great success in downloading packages and their depends .deb(s) into a directory, cd = change directory or opening a terminal in the folder and installing the things with «dpkg -i *.deb» but this is what’s refered to as «dependency hell».
ie: I don’t have net access have to go to Mcdonald’s, download all xyz package, then it’s depends and any of their depends onto a dang phone. Take em home, transfer to pc and install em all. Noooooooo ! Though dpkg does a great job of installing these packages in order and successful in my experience. Having a real hard time trying to figure what you’re doing and why. Some possible helpful commands related to this though and/or could make your situation even worse, depending. < PUN INTENDED.
Did you «sudo apt-get upgrade && sudo apt-get upgrade» the effected Debian install. Man am out of comments on this deal.
Most powerful FREE tech-support tool on the planet * HERE. *
-
theblueplll
- Posts: 154
- Joined: 2019-04-29 01:17
- Been thanked: 2 times
Re: Dpkg error can’t solve
#5
Post
by theblueplll » 2019-07-05 04:18
I am starting to wonder about the master drive in that machine actually.
I got the error fixed today finally
Code: Select all
apt -f install or was it install -f
worked. Although I tried that 2 nights ago more than once and it didn’t help.
But this keeps happening like every other day and today when i got home and turn it on and it was fine then all of a sudden it reboots itself and tries to tell me the OS is missing Oh boy.
So either someone is playing games(if so why did they go after the machine with nothing on it and not this one LoL) or somethings wrong with the machine itself.
I’ll have to run some tests on it I guess.
Thank you for the replies I really do appreciate people at trying to help.
-
Deb-fan
- Posts: 1047
- Joined: 2012-08-14 12:27
- Been thanked: 4 times
Re: Dpkg error can’t solve
#6
Post
by Deb-fan » 2019-07-05 17:11
Is it possible to partition and add a fresh os install. See if the oddities continue. Sounds really frustrating.
Most powerful FREE tech-support tool on the planet * HERE. *
-
theblueplll
- Posts: 154
- Joined: 2019-04-29 01:17
- Been thanked: 2 times
Re: Dpkg error can’t solve
#8
Post
by theblueplll » 2019-07-06 18:55
Head_on_a_Stick wrote:
theblueplll wrote:Could this be a hardware problem somehow? Maybe a bad hdd?
^ This.
Has to be some sort of hardware problem since 3 different fresh installs with 2 different ISO’s and this keeps happening.
-
GarryRicketson
- Posts: 5871
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: Dpkg error can’t solve
#9
Post
by GarryRicketson » 2019-07-06 20:04
If the hardware is suspected, that should be the first thing to check
Deb-fan wrote:Is it possible to partition and add a fresh os install. See if the oddities continue. Sounds really frustrating.
What would the point be in doing a fresh install on bad hardware ?
-
Deb-fan
- Posts: 1047
- Joined: 2012-08-14 12:27
- Been thanked: 4 times
Re: Dpkg error can’t solve
#10
Post
by Deb-fan » 2019-07-06 20:56
Hadn’t read closely enough to see he’d already been there, done it. Was thinking could rule out software/os issue perhaps. My bad, sorry if it’s in fact hardware bluepill, that stinks.
Most powerful FREE tech-support tool on the planet * HERE. *
-
theblueplll
- Posts: 154
- Joined: 2019-04-29 01:17
- Been thanked: 2 times
Re: Dpkg error can’t solve
#11
Post
by theblueplll » 2019-07-07 21:36
GarryRicketson wrote:If the hardware is suspected, that should be the first thing to check
Deb-fan wrote:Is it possible to partition and add a fresh os install. See if the oddities continue. Sounds really frustrating.
What would the point be in doing a fresh install on bad hardware ?
I SHOULD HAVE thought things through before I even started so I wouldn’t have had to post this.
I’m suspicous of the ATA cable that is in there since one of them broke the end off awful easily while removing it from the drive.
So I ordered some (need a couple for another «project machine» also).
I plan to switch out the cables and run a bunch of tests on the HDD and then go from there.
If the drive is toast not a big deal I have quite a few hanging around from parts I have collected over the years.
Thanks to all for trying to help.
- Печать
Страницы: [1] Вниз
Тема: Проблема после обновления (Прочитано 3554 раз)
0 Пользователей и 1 Гость просматривают эту тему.

nikkol22rus
Всем добрый день. Около 5 месяцев назад обновил систему на 16.04, проблем небыло, все встало нормально. Система стабильно обновлялось в интернете и с удовольствием тянул пакеты обновнления до недавнего времени. При последнем обновлении произошла ошибка broken count 0. С тех самых пор система не обновляется….указывая эту ошибку. При этом система предлогает ввести в терминале команду (скрин ниже) при этом терминал ругаеться на непонятные для него задачи…Что делать не знаю, может кто сведующий поможет.

Morisson
nikkol22rus, так ты делал, что там написано?

БТР
nikkol22rus, вывод терминала нужно копировать в текст сообщения.
выполните предложенную команду и сюда вывод под спойлер или в тег «код».

nikkol22rus
nikkol22rus, так ты делал, что там написано?
Неверная операция instal-f

EvangelionDeath
nikkol22rus,
sudo apt-get install -f
HP Pro 840 G3: Intel i5-6300U, 32GB DDR4 2133MHz, Intel 520, Intel Pro 2500 180GB/Ubuntu 22.04
Dell Latitude 5590: Intel i5-8350U, 16GB DDR4 2400MHz, Intel 620, Samsung 1TB/Ubuntu 22.04

Heider
Неверная операция instal-f
Пробел забыл воткнуть. Внимательно вводи команды.

nikkol22rus
Неверная операция instal-f
Пробел забыл воткнуть. Внимательно вводи команды.
Действительно….нужно было воткнуть пробел…, заработало…., после ввода началось удаление каких то пакетов…., по результатам отпишусь….

San4ozzZ
отпишусь я )
administrator@administrator-desktop:~$ sudo apt-get install -f
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Исправление зависимостей… Готово
Следующий пакет устанавливался автоматически и больше не требуется:
libcuda1-304
Для его удаления используйте «sudo apt autoremove».
Пакеты, которые будут УДАЛЕНЫ:
console-setup console-setup-linux kbd ubuntu-minimal
обновлено 0, установлено 0 новых пакетов, для удаления отмечено 4 пакетов, и 12 пакетов не обновлено.
не установлено до конца или удалено 3 пакетов.
Необходимо скачать 657 kБ архивов.
После данной операции, объём занятого дискового пространства уменьшится на 2 744 kB.
Хотите продолжить? [Д/н] д
Пол:1 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main i386 keyboard-configuration all 1.108ubuntu15.3 [657 kB]
Получено 657 kБ за 1с (436 kБ/c)
(Чтение базы данных … на данный момент установлено 252482 файла и каталога.)
Удаляется ubuntu-minimal (1.361.1) …
Удаляется console-setup (1.108ubuntu15.4) …
Удаляется console-setup-linux (1.108ubuntu15.4) …
Удаляется kbd (1.15.5-1ubuntu5) …
Обрабатываются триггеры для man-db (2.7.5-1) …
Обрабатываются триггеры для doc-base (0.10.7) …
Обработка 1 удалённый файл doc-base...
dpkg: ошибка при обработке пакета keyboard-configuration (--configure):
пакет keyboard-configuration не готов к настройке
настройка невозможна (текущее состояние: «half-installed»)
E: Sub-process /usr/bin/dpkg returned an error code (1)
administrator@administrator-desktop:~$
дополняю .
Сейчас не появляется ошибка .
после ввода комманд ,
когда искал ответ на вопрос , При загрузке выскакивает ошибка: Сервис поиска сетевых ресурсов отключен
sudo sed -i -e'/AVAHI_DAEMON_DETECT_LOCAL/s/1/0/' /etc/default/avahi-daemon
sudo service avahi-daemon start
и возможно отключения галочек
в Программы и обновления
Параметры для разработчиков.
Обновления ,официально не поддерживаемые обновления xenial-backports
« Последнее редактирование: 26 Декабря 2017, 15:21:12 от San4ozzZ »

Morisson
sudo service avahi-daemon start
Замаскируй его нафиг и все)

Alex Blehman
После очередного обновления появился баг — при наведении курсора на панель Unity пропадает всё, что есть на рабочем столе, остается только лиловый фон во всю площадь экрана. Панель уведомлений пропадает тоже 
Куда копать?
P.S. 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux
P.S.S. При загрузке ОС нет окна Grub с выбором вариантов — ни memtest ни recovery, сразу загружается окно входа в систему и ввода пароля.
« Последнее редактирование: 06 Января 2018, 18:29:36 от Alex Blehman »
JoyBook S33 1,9 ГиБ, Intel Core2 CPU P8400 @ 2.26×2 Графика Mobile GM45 Express Chipset x86/MMX/SSE2 32-разрядная Диск 243,9ГБ

nikkol22rus
А теперь то же самое только еще вот такая штукенция появилась
НОВЫЕ пакеты, которые будут установлены:
hedgewars-data
Обновлено 0 пакетов, установлено 1 новых пакетов, для удаления отмечено 0 пакетов, и 370 пакетов не обновлено.
Установлено или удалено не до конца 95 пакетов.
Необходимо скачать 0 B/141 MB архивов.
После данной операции, объём занятого дискового пространства возрастёт на 157 MB.
Хотите продолжить? [Д/н] д
(Чтение базы данных … на данный момент установлено 271522 файла и каталога.)
Подготовка к распаковке …/hedgewars-data_0.9.24.1-dfsg-2ubuntu1_all.deb …
Распаковывается hedgewars-data (0.9.24.1-dfsg-2ubuntu1) …
dpkg-deb (подпроцесс): разжимающий элемент архива: ошибка lzma: сжатые данные повреждены
dpkg-deb: ошибка: <decompress> subprocess returned error exit status 2
dpkg: ошибка при обработке архива /var/cache/apt/archives/hedgewars-data_0.9.24.1-dfsg-2ubuntu1_all.deb (—unpack):
не удалось скопировать извлечённые данные «./usr/share/games/hedgewars/Data/Music/Castle.ogg» в «/usr/share/games/hedgewars/Data/Music/Castle.ogg.dpkg-new»: неожиданный конец файла или потока
При обработке следующих пакетов произошли ошибки:
/var/cache/apt/archives/hedgewars-data_0.9.24.1-dfsg-2ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

БТР
nikkol22rus,
sudo apt-get clean
sudo apt-get update
sudo apt-get install -f

nikkol22rus
Действительно помогло, спс за помощь и совет. Я как понимаю что то было с пакетами, то ли не доскачались, то ли не доустановились….в связи с чем возникли проблемы……..
- Печать
Страницы: [1] Вверх
I have created a directory structure with an executable file. Following is the output of tree:
program-5
├── debian
│ ├── DEBIAN
│ │ ├── changelog
│ │ ├── compat
│ │ ├── control
│ │ ├── copyright
│ │ ├── docs
│ │ ├── emacsen-install.ex
│ │ ├── emacsen-remove.ex
│ │ ├── emacsen-startup.ex
│ │ ├── init.d.ex
│ │ ├── manpage.1.ex
│ │ ├── manpage.sgml.ex
│ │ ├── manpage.xml.ex
│ │ ├── menu.ex
│ │ ├── postinst.ex
│ │ ├── postrm.ex
│ │ ├── preinst.ex
│ │ ├── prerm.ex
│ │ ├── program.cron.d.ex
│ │ ├── program.debhelper.log
│ │ ├── program.default.ex
│ │ ├── program.doc-base.EX
│ │ ├── README.Debian
│ │ ├── README.source
│ │ ├── rules
│ │ └── watch.ex
│ └── usr
│ └── local
│ └── include
│ └── myprog
│ ├── file.txt
└── program *(executable)*
This however, is not working with «file.txt». I want this file to go into /usr/local/include/myprog/ but that is not happening. it’s giving me the error:
(Reading database ...
(Reading database ... 5%
...
(Reading database ... 100%
(Reading database ... 204105 files and directories currently installed.)
Unpacking program-v5 (from .../program-5_1.4.2_i386.deb) ...
dpkg: error processing /tmp/program-5/debian/program-5_1.4.2_i386.deb (--install):
trying to overwrite '/usr/local/include/myprog/file.txt', which is also in package program2 20120329-1
dpkg-deb (subprocess): data: internal gzip write error: Broken pipe
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg-deb (subprocess): failed in write on buffer copy for failed to write to pipe in copy: Broken pipe
Errors were encountered while processing:
/tmp/program-5/debian/program-5_1.4.2_i386.deb
Can anyone offer any advice?
asked Mar 29, 2012 at 14:12
0
The error is pretty clear: You try to install program-v5 and it attempts to overwrite a file already present and owned by package program2.
So you need to either
-
manually uninstall
program2before installingprogram-v5, or -
add the required
Conflicts:,Provides:,Replaces:flags indebian/control— see the docs.
Lastly, for packages, /usr is a more natural choice then /usr/local.
answered Mar 29, 2012 at 14:18
Dirk EddelbuettelDirk Eddelbuettel
355k56 gold badges634 silver badges719 bronze badges
From the error message:
trying to overwrite ‘/usr/local/include/myprog/file.txt’, which is
also in package program2
It looks like you have a package program2 already installed on your system that have already installed this file usr/local/include/myprog/file.txt.
You should first uninstall this package dpkg -r program2
answered Mar 29, 2012 at 14:20
Didier TrossetDidier Trosset
35.7k13 gold badges87 silver badges122 bronze badges
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
LittleScriptMan
- Level 3
- Posts: 159
- Joined: Thu Jan 13, 2022 8:42 am
[SOLVED] dpkg errors with apturl package 0.5.2+linuxmint12 fixed by version 0.5.2+linuxmint13
Tried this morning to update apturl package version 0.5.2+linuxmint12 as suggested in Update Manager but got these errors in return
/var/cache/apt/archives/apturl_0.5.2+linuxmint12_all.deb uses an unknown compression process for control.tar.zst
and :
dpkg-deb —control subprocess returned error exit status 2
(which seems to be an unpack error probably caused by the unability to perform decompression of the archive).
Thanks for any help or suggestion.
PS : quick insight of the system (inxi -GS + Repos) — Kernel upgrade was necessary to allow wifi connection which didn’t work with 5.10 serie
Code: Select all
System: Host: asus4770 Kernel: 5.16.0-0.bpo.4-rt-amd64 x86_64 bits: 64 Desktop: Cinnamon 5.2.7 Distro: LMDE 5 Elsie
Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel
Device-2: NVIDIA GM107M [GeForce GTX 850M] driver: nouveau v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.3.5
Repos: Packages: 2177 apt: 2159 flatpak: 18
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com elsie main upstream import backport #id:linuxmint_main
2: deb https: //deb.debian.org/debian bullseye main contrib non-free
3: deb https: //deb.debian.org/debian bullseye-updates main contrib non-free
4: deb http: //security.debian.org bullseye-security main contrib non-free
5: deb https: //deb.debian.org/debian bullseye-backports main contrib non-free
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 4 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Interests : Firefox, Cinnamon & Bash Scripts
LM Version : LMDE5 (LMDE4 just in case)
-
karlchen
- Level 22
- Posts: 16879
- Joined: Sat Dec 31, 2011 7:21 am
- Location: Germany
Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)
Post
by karlchen » Mon Jun 20, 2022 6:52 am
Hello, LittleScriptMan. Hello, Abu.
Foreword:
At this point in time I can only crosscheck with LM 19.3, apturl 0.5.2+linuxmint8. LM 19.3 is not LMDE, so my findings may or may not be relevant.
Inner archive format of apturl.deb package
The inner archives in apturl 0.5.2+linuxmint8 is still .xz. No problem reading and extracting .xz archives here.
But on LMDE 4 and LMDE 5 the latest apturl 0.5.2+linuxmint12 has got inner archives of the format .zst.
In order to read .zst archives you seem to need a package simply named zstd.
By default this package is not pre-installed on LM 19.3.
I am not sure whether it will really resolve your problem.
Check whether zstd is available on your LMDE systems. Command: which zstd
In case this comes back empty, you might install zstd from the software repos.
Command: sudo apt-get install zstd
This might be sufficient to enable the Update Manager to read and install the apturl package 0.5.2+linuxmint12.
It is imaginable, however, that Update Manager will not use the commandline tool zstd, but instead some supporting library, which provides .zst archive reading capabilities.
In this case, you will have to wait for advice given by other LMDE users.
Update/Solution:
As explained in Clem’s post further down , the problem has been resolved by publishing a corrected apturl 0.5.2+linuxmint13.
So refresh your list of available software updates. It should display apturl 0.5.2+linuxmint13. The inner archives are in .xz format again. The installation should succeed.
Regards,
Karl
Last edited by karlchen on Mon Jun 20, 2022 7:55 am, edited 2 times in total.
Reason: Update/Solution: see Clem’s post further down. The corrected apturl package is «apturl 0.5.2+linuxmint13»
The people of Alderaan keep on bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine.
The Prophet’s Song
-
cpedretti
- Level 3
- Posts: 186
- Joined: Tue Mar 10, 2020 12:06 am
Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)
Post
by cpedretti » Mon Jun 20, 2022 7:02 am
karlchen wrote: ↑
Mon Jun 20, 2022 6:52 am
Hello, LittleScriptMan. Hello, Abu.Foreword:
At this point in time I can only crosscheck with LM 19.3, apturl 0.5.2+linuxmint8. LM 19.3 is not LMDE, so my findings may or may not be relevant.Inner archive format of apturl.deb package
The inner archives in apturl 0.5.2+linuxmint8 is still .xz. No problem reading and extracting .xz archives here.
But on LMDE 4 and LMDE 5 the latest apturl 0.5.2+linuxmint12 has got inner archives of the format .zst.In order to read .zst archives you seem to need a package simply named zstd.
By default this package is not pre-installed on LM 19.3.I am not sure whether it will really resolve your problem.
Check whether zstd is available on your LMDE systems. Command:which zstd
In case this comes back empty, you might install zstd from the software repos.
Command:sudo apt-get install zstd
This might be sufficient to enable the Update Manager to read and install the apturl package 0.5.2+linuxmint12.
It is imaginable, however, that Update Manager will not use the commandline tool zstd, but instead some supporting library, which provides .zst archive reading capabilities.
In this case, you will have to wait for advice given by other LMDE users.Regards,
Karl
Hi, have the same issue, after installing the zstd package, error was same after update && upgrade :/
AMD Ryzen 7 3700X — 32GB DDR4 — Asus GTX1660TI EVO — SSD SAMSUNG EVO 860 — Mobo Gigabyte AORUS ELITE B550 V2 — PSU Gigabyte 750W Gold — Case Zalman X3 White
LMDE5 / W11
-
chiefjim
- Level 6
- Posts: 1157
- Joined: Sun Jun 07, 2009 7:26 am
- Location: South Texas, USA
Re: dpkg errors with last apturl package (version 0.5.2+linuxmint12)
Post
by chiefjim » Mon Jun 20, 2022 7:30 am
abu wrote: ↑
Mon Jun 20, 2022 6:15 am
You’re not alone. Same here with LMDE4, but I don’t have any solution.
Was going to make an original posting but see others beat me to it. Same problem here.
Mint-21.0 Mate 64 bit / LMDE-5 64 bit
Gigabyte H370M D3H
Intel G3258
Crucial Ballistic Sport 32GB DDR4 2400
8TB HDD Seagate Baracuda 5400rpm
-
clem
- Level 12
- Posts: 4266
- Joined: Wed Nov 15, 2006 8:34 am
- Contact:
-
Maxwell-J
- Level 4
- Posts: 262
- Joined: Fri Nov 12, 2021 6:10 pm
While attempting to install the package sw-nginx I encountered the following error messages:
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/327 kB of archives.
After this operation, 813 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
sw-nginx
Authentication warning overridden.
(Reading database ... 149469 files and directories currently installed.)
Unpacking sw-nginx (from .../sw-nginx_1.6.0-1.14051516.debian70_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/sw-nginx_1.6.0-1.14051516.debian70_amd64.deb (--unpack):
trying to overwrite '/etc/logrotate.d/nginx', which is also in package nginx 1.6.2-1~wheezy
dpkg-deb (subprocess): decompressing archive member: internal gzip write error: Broken pipe
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg-deb (subprocess): cannot copy archive member from '/var/cache/apt/archives/sw-nginx_1.6.0-1.14051516.debian70_amd64.deb' to decompressor pipe: failed to write (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/sw-nginx_1.6.0-1.14051516.debian70_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Error: An error occurred on attempt to install packages.
Attention! Your software might be inoperable.
Please, contact product technical support.
How can I install this package?
slm♦
356k112 gold badges753 silver badges860 bronze badges
asked Sep 22, 2014 at 0:51
4
I figured out how to work around my issue by doing the installation like so:
$ sudo dpkg -i --force-overwrite packagename
It would appear that I was getting collisions from a different nginx package that had files in common with this new package. I opted for the heavy handed method and simply did the above, --force-overwrite.
DO NOT USE 
answered Sep 22, 2014 at 1:10
2
on a Ubuntu 12.04 Server I´m trying to update PHP 5.3 to 5.5 this is what I have done:
sudo add-apt-repository ppa:ondrej/php5
sudo apt-get update
sudo apt-get install php5
unfortuntely the installation ends with following error:
dpkg: error processing /var/cache/apt/archives/apache2-bin_2.4.16-4+deb.sury.org~precise+4_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man8/apache2.8.gz', which is also in package apache2.2-common 2.2.22-1ubuntu1.10
dpkg-deb (subprocess): subprocess data was killed by signal (Broken pipe)
dpkg-deb: error: subprocess <decompress> returned error exit status 2
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/apache2-bin_2.4.16-4+deb.sury.org~precise+4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
It seems PHP 5 affects Apache 2.2 as well. Thankful for help why the subprocess was killed.
EDIT: I solved this by uninstalling apache2.2 completely and reinstalling 2.4 which worked without errors.
asked Nov 23, 2015 at 17:13
tonitoni
1396 bronze badges
4
I got same problem when upgrade PHP, you can try this
sudo dpkg -i --force-overwrite /var/cache/apt/archives/apache2-bin_2.4.16-4+deb.sury.org~precise+4_amd64.deb
and then install php5 by
sudo apt-get -f install php5
this will upgrade apache2, enjoy it.
answered Jan 26, 2016 at 6:23








