Ubuntu error while installing package

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:

Not a Debian format archive

• Bug : provide a master report

This error indicated that the header of the .deb archive is not recognized as a valid debian format.

dpkg-deb: `/var/cache/apt/archives/libswscale0_4%3a0.5+svn20090706-2ubuntu2_i386.deb' is not a debian format archive 
dpkg: error processing /var/cache/apt/archives/libswscale0_4%3a0.5+svn20090706-2ubuntu2_i386.deb (--unpack): 
 subprocess dpkg-deb --control returned error exit status 2

Corrupted filesystem tarfile

• Bug 320743

Unpacking libaccess-bridge-java (from .../libaccess-bridge-java_1.24.0-0ubuntu2_all.deb) ...
dpkg: error processing /var/cache/apt/archives/libaccess-bridge-java_1.24.0-0ubuntu2_all.deb (--unpack):
 corrupted filesystem tarfile - corrupted package archive
dpkg-deb: subprocess paste killed by signal (Broken pipe)

—fsys-tarfile

• Bug : provide a master report

Unpacking replacement audacity-data ...
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing /var/cache/apt/archives/audacity-data_1.3.7-2ubuntu1_all.deb (--unpack):
 subprocess dpkg-deb --fsys-tarfile returned error exit status 2
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/audacity-data_1.3.7-2ubuntu1_all.deb

short read — Input/output error

• Bug : provide a master report

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:

Unpacking linux-image-2.6.27-11-generic (from .../linux-image-2.6.27-11-generic_2.6.27-11.24_i386.deb) ...
Done.
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing /var/cache/apt/archives/linux-image-2.6.27-11-generic_2.6.27-11.24_i386.deb (--unpack):
 short read in buffer_copy (backend dpkg-deb during `./lib/modules/2.6.27-11-generic/kernel/drivers/infiniband/core/ib_uverbs.ko')

or

Unpacking replacement libfreetype6 ...
dpkg-deb (subprocess): error in buffer_read(stream): failed to write to pipe in copy: Input/output error
dpkg-deb: subprocess paste returned error exit status 2
dpkg: error processing /var/cache/apt/archives/libfreetype6_2.3.9-4ubuntu0.1_i386.deb (--unpack):
 short read in buffer_copy (backend dpkg-deb during `./usr/lib/libfreetype.so.6.3.20')

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

• Bug : 512096

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

Setting up flashplugin-installer (10.0.32.18ubuntu1) ...
dpkg (subprocess): unable to execute installed post-installation script: Exec format error
dpkg: error processing flashplugin-installer (--configure):
 subprocess installed post-installation script returned error exit status 2

During removal of a package

Removing gnome-do ...
dpkg (subprocess): unable to execute installed pre-removal script: Exec format error
dpkg: error processing gnome-do (--purge):
 subprocess installed pre-removal script returned error exit status 2

Workaround A: Finish the install

Workaround B: Remove the package and reinstall

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

• Bug 500042

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

Setting up ureadahead (0.90.3-2) ...
dpkg: error processing ureadahead (--configure):
 triggers ci file contains unknown directive syntax

Workaround

lzma : decoder error

• Bug : provide a master report

Unpacking openjdk-6-jre-lib (from .../openjdk-6-jre-lib_6b12-0ubuntu6_all.deb) ...
lzma: Decoder error
dpkg-deb: subprocess <decompress> returned error exit status 1
dpkg: error processing /var/cache/apt/archives/openjdk-6-jre-lib_6b12-0ubuntu6_all.deb (--unpack):
 short read in buffer_copy (backend dpkg-deb during `./usr/lib/jvm/java-6-openjdk/jre/lib/ext/localedata.jar')

files list file missing final newline / contains empty filename

• Bug 108189

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

Selecting previously deselected package linux-source-2.6.27.
(Reading database ... dpkg: error processing /var/cache/apt/archives/linux-source-2.6.27_2.6.27-9.19_all.deb (--unpack):
 files list file for package `libpoppler-glib3' 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):

dpkg -c /var/cache/apt/archive/libgnome2-0_2.24.1-0ubuntu3_i386.deb | awk 
‘{if ($6 == «./») { print «/.»; } 
else if (substr($6, length($6), 1) == «/») 
{print substr($6, 2, length($6) — 2); } 
else { print substr($6, 2, length($6) — 1);}}’ 
> /var/lib/dpkg/info/libgnome2-0.list

Inconsistent state

Package in bad inconsistent state

• Bug : provide a master report

Removing flashplugin-nonfree ...
dpkg: error processing flashplugin-installer (--purge):
 Package is in a very bad inconsistent state - you should
 reinstall it before attempting a removal.

Workaround A:

Workaround B:

package is already installed and configured

• Bug : 541595

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’.

dpkg: error processing language-pack-ar (--configure):
 package language-pack-ar is already installed and configured

Workaround A:

Workaround B:

Other issues

Can’t access archive

• Bug : 523395

The source of this error is not clearly identified and needs further investigation (see comment #3 of the master report)

dpkg: error processing /media/cdrom0//pool/main/g/gcc-4.4/libstdc++6-4.4-dev_4.4.1-4ubuntu8_i386.deb (--unpack):
 cannot access archive: No such file or directory
dpkg: error processing /media/cdrom0//pool/main/g/gcc-4.4/g++-4.4_4.4.1-4ubuntu8_i386.deb (--unpack):
 cannot access archive: No such file or directory

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.

Unpacking replacement perl-base ...
dpkg: error processing /var/cache/apt/archives/perl-base_5.10.0-11.1ubuntu2.2_i386.deb (--unpack):
 failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during `./usr/lib/perl/5.10.0/IO.pm': No space left on device

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

• Bug 349469

• Bug 377211

debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

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

• Bug 386763

Under certain circumstances font packages failed to install with the following error:

Setting up ttf-dejavu-extra (2.28-1) ...
E: /var/lib/defoma/locked exists.
E: Another defoma process seems running, or you aren't root.
E: If you are root and defoma process isn't running undoubtedly,
E: it is possible that defoma might have aborted.
E: Please run defoma-reconfigure -f to fix its broken status.
dpkg: error processing ttf-dejavu-extra (--configure):
 subprocess post-installation script returned error exit status 1

Workaround

Open a terminal (Applications -> Accessories -> Terminal ) and run the following command:

$ sudo defoma-reconfigure -f

/etc/defoma/hints/FONTNAME.hints: Unable to open, or empty

• Bug 521431

Under certain circumstances font packages failed to install with the following error:

Setting up ttf-konatu (24-3) ...
/etc/defoma/hints/ttf-konatu.hints: Unable to open, or empty.
dpkg: error processing ttf-konatu (--configure):
 subprocess installed post-installation script returned error exit status 1

This is due to a corrupted hint file.

Workaround

To workaround it, open a terminal and run the following commands:

$ sudo rm /var/lib/dpkg/info/FONTNAME.prerm
$ sudo apt-get remove --purge FONTNAME
$ sudo apt-get clean

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

• Bug 493572

• Bug 478841

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:

Setting up python-dateutil (1.4.1-2) ...
Segmentation fault
dpkg: error processing python-dateutil (--configure):
 subprocess post-installation script returned error exit status 139

There is not much we can do except the advice below:

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

• Kernel specific errors

• Debugging Update manager

TODO

• 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

• Add section with common install/upgrade issues for specific packages ? only provide list of report + description ?

CategoryBugSquad CategoryDebugging

Introduction

Linux packages are compressed archives containing programs and files necessary to run them. The package distribution system is designed to be robust and simplify the application installation process.

However, a bad internet connection or misconfigured third-party installers can corrupt packages and cause problems on your system.

This article will show you how to troubleshoot and fix broken packages on Ubuntu using the available APT and DPKG tools.

Prerequisites

• An account with sudo privileges
• An Ubuntu system

Check for Updates

Start troubleshooting by rebuilding the list of dependencies. The --fix-missing option tells APT to ignore missing packages. The option ensures the update process is performed without APT returning an error.

sudo apt update --fix-missing

Force APT to Correct Missing Dependencies or Broken Packages

Missing package dependencies are a common reason for package-related errors.

1. Use apt install with the -f flag to tell APT to locate the missing packages and install them.

sudo apt install -f

APT lists the missing packages on your system.

2. Press ENTER to start the installation.

Force Reconfigure or Remove Broken Packages with DPKG

Broken packages may cause package manager configuration problems.

1. Reconfigure DPKG, the base package management system, with the following command:

sudo dpkg --configure -a

2. Check if DPKG marked some packages as needing a reinstall.

sudo dpkg -l | grep ^..R

3. If the command above returns a list of one or more packages, try removing the packages by typing:

sudo dpkg --purge --force-all [package-name]

The example below shows how to remove the corrupted vlc-plugin-base package.

4. After you finish troubleshooting, run the following command to clean up the system:

sudo apt clean

5. Then update the repositories again:

sudo apt update

Resolve DPKG Lock Issue

The DPKG lock error appears when trying to install a package while another process is using DPKG.

However, sometimes the error occurs even if no other processes are using the package management system.

1. To fix the problem, remove the lock file manually:

sudo rm /var/lib/apt/lists/lock

2. Also, remove the lock in cache:

sudo rm /var/cache/apt/archives/lock

Deleting the lock enables you to use APT and DPKG again.

Conclusion

The article provided common ways of resolving problems caused by broken packages on Ubuntu.

For more information related to package management on Ubuntu, read:

• How to List Installed Packages on Ubuntu
• A Comprehensive Guide to Using Snap Packages on Ubuntu
• How to Install Deb Files (Packages) on Ubuntu

Everyone faces a ton of errors and difficulties when we migrate to a new environment/operating system. The errors may vary from app installation errors to common usage errors.

Errors are pretty common when you shift from a full GUI-based operating system to a semi-command-based operating system like Ubuntu. In the Linux community, there is a saying, if you don’t get any errors while using Linux, this means that you are not properly using the system.

Linux OSs like Ubuntu and Mint is considered as one of the easiest Linux as you can do everything with the graphical user interface. But OSs like Arch Linux are totally command based unless you are using any desktop environment.

We, in this article, tried to cover the widespread errors and their solutions in as simple as possible straightforward methods/steps. Follow carefully and let us know whether you ended in solving the error or not.

Fix All Application Installation Error in Linux

Here are the Best Solutions to Fix Various Types of Software Application Installation Error on Linux PC System

Error Type 1: sub-process /usr/bin/dpkg returned an error code (1)

This is one of the common errors Ubuntu or any Debian based distros faces while installing any software package from either terminal or software center.

This is one of the examples we encountered while updating the Chrome Stable package. This means either the corrupt or broken.

Fix 1: Reconfiguring the dpkg package database

We are going to use a simple command to reconfigure the dpkg database, as this error may be caused due to any interruption while the installation.

$ sudo dpkg --configure -a

After executing this command, try the installation, and check if you are facing the same error or not. If yes then proceed to Fix 2.

Fix 2: Force Installation of the Package

Since the dpkg was not the issue, try this command to forcefully install the troublesome package.

We are going to show you two different commands, which actually work in a similar way, it will fix the broken dependencies to terminate the error.

$ sudo apt install -f

or

$ sudo apt install--fix-broken

Error Type 2: could not get lock /var/lib/dpkg/lock

This error can be encountered while using the apt-get command in the terminal. This error basically says us that the dpkg is not currently available to use. This can explain two things, there is already an app is being installed, or the app installation was interrupted in the middle of the process.

The error usually looks like this,

Could not get lock /var/lib/dpkg/lock – open (11: Resource temporarily unavailable)

E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

or

E: Could not get lock /var/lib/apt/lists/lock – open (11: Resource temporarily unavailable)

E: Unable to lock directory /var/lib/apt/lists/

E: Could not get lock /var/lib/dpkg/lock – open (11: Resource temporarily unavailable)

E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

Fix 1: Find and Kill the Process

In this method, we are manually going to find the process which is running and then will have to manually stop/kill the process(es).

First, use the following command to search the running process(es),

$ ps aux | grep [a]pt

or

$ pgrep -a apt

Now you have the process number, we are going to use the following command to kill the process,

$ sudo kill process_number

or

$ sudo kill -9 process_number

If you don’t search and figure out the process number/process id, use the following command to kill all the ongoing process(es),

$ sudo killall apt apt-get

Fix 2: By Deleting the Lock

In case, the above fix didn’t work in your case, we will try to delete the lock to get rid of the error, use the following command to do so,

$ sudo rm /var/lib/apt/lists/lock

$ sudo rm /var/cache/apt/archives/lock

$ sudo rm /var/lib/dpkg/lock

Execute these commands one by one, and cross verify the lock directory from the error itself and then use the rm command. For example, if your error contains /var/cache/apt/archives/lock, then only use the directory.

Error Type 3: add-apt-repository: command not found

This error is encountered when you are trying to add a new software from the PPA (Personal Package Archive) repository. PPA is one of the many ways that is used to install software into the Linux system.

We are first going to use the following command to update/sync the repository database,

$ sudo apt-get update

If the execution completes without any error then only proceed to the next step.

Actually, add-apt-repository isn’t like the other command package found in Ubuntu/Debian systems, we are going to install the software-properties-common package to install the add-apt-repository.

$ sudo apt-get install software-properties-common

Error Type 4: E: Unable to locate package

This is one of the errors I used to face whenever I use to try the apt-get or apt command to install any package. Well if we take a deep look into the error, the error is self-explanatory, that the system couldn’t find the package to install.

This error will look like this,

$ sudo apt-get install package_name

Reading package lists… Done

Building dependency tree

Reading state information… Done

E: Unable to locate package package_name

Now, the error is self-explanatory, but is it the same case with the solution too? I am worried to say that it is not.

Fix 1: Check Package Name

We are going to start with a simple solution, check for typos, spelling mistakes, if this is not the case with your situation, then we will have to look for other solutions.

Fix 2: Check the Compatibility of the Package

Now, we are going to check whether the package is available for your version of Ubuntu or not.

Use the following command to check your Ubuntu Version (Release and Codename),

$ lsb_release -a

Now, we know the release and codename of our Ubuntu (In our case 20.04 Focal), we will head to the Ubuntu Package Manager Website.

Scroll down to the search section, and search the package you were trying to install,

If the package is not available in the repository, then it is not possible to install that package on your Linux machine.

Error Type 5: Failed to download repository information

Many new Linux users prefer the GUI based Software Center to install new applications/software. This “Failed to download repository information” error is encountered in that Software Center only.

The error looks like this,

As you can see that the error also says to ‘Check your internet connection’, but it is weird as the internet is perfectly working.

In this case, the only solution is to update the apt repository and observe the result to figure out the original error that is occurring that pop-up.

$ sudo apt update

In the above result, see the last two lines of the result, it can be different in your case, note that error and comment below, we will be more than happy to help you out. Also, alternatively, you can search for that error in any Ubuntu community to see the solution to that particular error.

Error Type 6: Failed to download package files

This is another similar error to the above ‘Failed to download package files’ error, but the good thing about this error is that it is solvable.

The error says that the new version of the already installed software is available but it is not available to that particular mirror, so we will have to connect to the main server to update the issue.

For connecting to the main server, open Software & Updates and select the Main server from the drop-down menu of the ‘Download from’ label.

Conclusion: Fix all Linux App Install Errors on your Unbuntu System with this detailed guide listed above. If you have any query please comment below 🙂

If you’ve any thoughts on How to Fix All App Installation Errors in Linux?, then feel free to drop in below comment box. Also, please subscribe to our DigitBin YouTube channel for videos tutorials. Cheers!