Shulou(Shulou.com)06/01 Report--

This article is to share with you about UBUNTU update source errors how to solve, the editor feels very practical, so share with you to learn, I hope you can learn something after reading this article, do not say much, follow the editor to have a look.

Merge list question

When you run the update command in the terminal, you may encounter this error "merge list error", like this:

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:

Sudo rm-r / var/lib/apt/lists/*

Sudo apt-get clean & & sudo apt-get update

Failed to download warehouse information-1

In fact, there are two types of download repository information failure errors. If your mistake is like this:

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 fix it with the following command:

Sudo rm-rf / var/lib/apt/lists/*

Sudo apt-get update

Failed to download warehouse information-2

Another type of failure to download repository information is due to the obsolescence of PPA. Typically, when you run the Update Manager and see an error like this:

You can run sudo apt-get update to see which PPA update failed, and you can remove it from the source list. You can follow this screenshot guide to fix the failure to download warehouse information.

Failed to download package file error

A similar error is a failure to download the package file, like this:

This error is easy to fix, you only need to modify the software source as the master server. Go to "Software and updates", where you can modify the download server as the primary server:

Partial update error

Running an update in a terminal will result in some update errors:

Not all updates can be installed

Run a partial upgrade, to install as many updates as possible

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

Sudo apt-get install-f

An error occurred while loading shared libraries

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

This error can be fixed by running the following command in the terminal:

Sudo / sbin/ldconfig-v

You can find more details here. An error occurred while loading the shared library.

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

This error occurs when another program is using 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/

Usually, this problem will be fine as long as you turn off all other programs that use apt. However, if the problem persists, you can use the following command:

Sudo rm / var/lib/apt/lists/lock

If the above command doesn't work, you can try this command:

Sudo killall apt-get

More information about the error can be found here.

GPG error: the following signatures cannot be verified

When adding a PPA, it may result in the following error GPG error: the following signatures cannot be verified, which usually occurs when running an update in 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 have to do is get the public key in the system and get the key number from the information. In the above information, the key number is 68980A0EA10B4DE8. The key can be used in the following ways:

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

After adding the key, there will be no problem running the update again.

BADSIG error

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

W: An 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 the BADSIG error, use the following command in the terminal:

Sudo apt-get clean

Cd / var/lib/apt

Sudo mv lists oldlist

Sudo mkdir-p lists/partial

Sudo apt-get clean

Sudo apt-get update

This article is a collection of Ubuntu update errors that you may encounter, and I hope this will help you deal with them. Have you encountered any other update errors in Ubuntu? Please tell me in the comments below that I will try to write a quick guide.

Here are some additions from other netizens

There is a problem with the update source

E: Problem executing scripts APT::Update::Post-Invoke-Success'if / usr/bin/test-w / var/cache/app-info-a-e / usr/bin/appstreamcli; then appstreamcli refresh > / dev/null; fi'

E: Sub-process returned an error code

Solution.

Sudo pkill-KILL appstreamcli

Wget-P / tmp https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb

Sudo dpkg-I / tmp/appstream_0.9.4-1ubuntu1_amd64.deb / tmp/libappstream3_0.9.4-1ubuntu1_amd64.deb

Then ok in this update.

E: GPG error: http://mirrors.163.com precise Release: invalid signature: NODATA 1 NODATA 2

This error indicates that you are not connected to the Internet. Check the status of the network.

When adding a source, and then interrupting the update in the middle of updating the source, there will be an error message as long as you reinstall the software or update it again.

E: unable to acquire lock / var/lib/apt/lists/lock-open (11: resource temporarily unavailable) E: unable to lock directory / var/lib/apt/lists/

Input instruction: sudo rm / var/lib/apt/lists/lock

The above is how to solve the errors in the UBUNTU update source. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.