Ubuntu update error repair Overview

Ubuntu update error repair Overview

In the Ubuntu update, who did not encounter an error? In Ubuntu and other Ubuntu-based Linux distributions, update errors are common and often occur. These errors are caused by a variety of causes and are easy to fix. In this article, we will see various types of frequently occurring update errors in Ubuntu and their repair methods.

 

Merge list problems

When you run the update command on the terminal, you may encounter the "merge list error" error, as shown below:

E:Encountered a section with no Package: header,
E:Problem with MergeList /var/lib/apt/lists/archive.ubuntu.comubuntudistspreciseuniversebinary-i386Packages,
E:The package lists or status file could not be parsed or opened.’

You can use the following command to fix the error:

1. sudo rm -r /var/lib/apt/lists/*
2. sudo apt-get clean && sudo apt-get update

 

Failed to download Repository Information-1

In fact, there are two types of download Warehouse Information failure errors. If your error is as follows:

W:Failed to fetch bzip2:/var/lib/apt/lists/partial/in.archive.ubuntu.comubuntudistsoneiricrestrictedbinary-i386Packages Hash Sum mismatch,
W:Failed to fetch bzip2:/var/lib/apt/lists/partial/in.archive.ubuntu.comubuntudistsoneiricmultiversebinary-i386Packages Hash Sum mismatch,
E:Some index files failed to download. They have been ignored, or old ones used instead

Then, you can use the following command to fix the problem:

1. sudo rm -rf /var/lib/apt/lists/*
2. sudo apt-get update

 

Failed to download Repository Information-2

Another type of failure in downloading repository information is caused by the expiration of PPA. Generally, when you run the update manager and see an error like this:

You can run sudo apt-get update to check which PPA failed to update. You can delete it from the source list. You can follow this guide to fix the failure of downloading repository information.

 

An error occurred while downloading the package file.

A similar error is an error occurred while downloading the package file, as shown in the following code:

This error can be easily fixed by modifying the software source to the master server. Go to "software and updates", where you can modify and download the server as the master server:

 

Some update errors

Some update errors may occur when you run updates on the terminal:

Not all updates can be installed
Run a partial upgrade, to install as many updates as possible

Run the following command on the terminal to fix the error:

1. sudo apt-get install -f

 

An error occurred while loading the shared library.

This error is more of an installation error than an update error. If you try to install the program from the source code, you may encounter this error:

error while loading shared libraries:
cannot open shared object file: No such file or directory

You can fix this error by running the following command on the terminal:

1. sudo /sbin/ldconfig -v

You can find more details here, and an error occurs when loading the shared library.

 

Unable to obtain lock/var/cache/apt/archives/lock

This error occurs when another program uses APT. Suppose you are installing something in the Ubuntu Software Center, and then you try to run apt in the terminal.

E: Could not get lock /var/cache/apt/archives/lock – open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/cache/apt/archives/

Generally, this problem will be fine if you shut down all other apt-enabled programs. However, if the problem persists, run the following command:

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

If the preceding command does not work, try the following command:

1. sudo killall apt-get

For more information about this error, refer to here.

 

GPG error: The following signature cannot be verified

When you add a PPA, the following GPG errors may occur: The following signatures cannot be verified, which usually occurs when an update is run on the terminal:

W: GPG error: http://repo.mate-desktop.org saucy InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 68980A0EA10B4DE8

All we need to do is get the public key in the system and get the key number from the information. In the preceding information, the key number is 68980A0EA10B4DE8. This key can be used in the following ways:

1. sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68980A0EA10B4DE8

After the key is added, it is no problem to run the update again.

 

BADSIG Error

Another Ubuntu update error related to the signature is a BADSIG error, which looks like this:

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://extras.ubuntu.com precise Release: The following signatures were invalid: BADSIG 16126D3A3E5C1192 Ubuntu Extras Archive Automatic Signing Key
W: GPG error: http://ppa.launchpad.net precise Release:
The following signatures were invalid: BADSIG 4C1CBC1B69B0E2F4 Launchpad PPA for Jonathan French W: Failed to fetch http://extras.ubuntu.com/ubuntu/dists/precise/Release

To fix this BADSIG error, run the following command on the terminal:

1. sudo apt-get clean
2. cd /var/lib/apt
3. sudo mv lists oldlist
4. sudo mkdir -p lists/partial
5. sudo apt-get clean
6. sudo apt-get update

This article brings together the Ubuntu update errors you may encounter. I hope this will help you handle these errors. Have you ever encountered any other update errors in Ubuntu? Please let me know in the following comments that I will try to write a Quick Guide.