There Was an Error While Updating: Login Error. Please Login Again. (-3333)
Who hasn't come across an error while doing an update in Ubuntu? Update errors are mutual and plenty in Ubuntu and other Linux distributions based on Ubuntu. Here are some common Ubuntu update errors and their fixes.
This article is part of Ubuntu beginner series that explains the know-how of Ubuntu so that a new user could empathize the things better.
In an earlier article, I discussed how to update Ubuntu. In this tutorial, I'll discuss some mutual errors you may encounter while updating Ubuntu. Information technology usually happens because you tried to add software or repositories on your ain and that probably caused an issue.
There is no demand to panic if y'all meet the errors while updating your organisation.The errors are common and the fix is easy. You'll acquire how to set up those mutual update errors.
Before you brainstorm, I highly suggest reading these two articles to have a better understanding of the repository concept in Ubuntu.
Empathise Ubuntu repositories
Learn what are various repositories in Ubuntu and how they enable yous to install software in your system.
Understanding PPA in Ubuntu
Farther improve your concept of repositories and packet handling in Ubuntu with this detailed guide on PPA.
Mistake 0: Failed to download repository information
Many Ubuntu desktop users update their organisation through the graphical software updater tool. You are notified that updates are available for your system and yous tin can click ane push to start downloading and installing the updates.
Well, that'south what usually happens. But sometimes you'll see an error like this:
Failed to download repository information. Check your internet connection.
That's a weird error because your internet connection is about likely working merely fine and it still says to cheque the internet connection.
Did you note that I chosen it 'error 0'? It'southward because it's non an mistake in itself. I hateful, most probably, information technology has nothing to do with the net connection. But there is no useful data other than this misleading fault message.
If you lot see this fault message and your cyberspace connectedness is working fine, it'southward time to put on your detective hat and use your gray cells (equally Hercule Poirot would say).
You'll have to use the command line here. Yous tin use Ctrl+Alt+T keyboard shortcut to open the terminal in Ubuntu. In the terminal, use this command:
sudo apt update Let the command end. Find the final three-four lines of its output. That will requite you the real reason why sudo apt-get update fails. Hither'south an example:
Residual of the tutorial hither shows how to handle the errors that yous only saw in the last few lines of the update command output.
Fault one: Problem With MergeList
When you run update in terminal, you may see an error "problem with MergeList" like beneath:
E:Encountered a section with no Package: header, E:Trouble with MergeList /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_precise_universe_binary-i386_Packages, E:The parcel lists or status file could non be parsed or opened.'
For some reasons, the file in /var/lib/apt/lists directory got corrupted. You tin can delete all the files in this directory and run the update once again to regenerate everything anew. Use the post-obit commands one by one:
sudo rm -r /var/lib/apt/lists/* sudo apt-become make clean && sudo apt-get update Your problem should exist fixed.
Error 2: Hash Sum mismatch
If you find an error that talks about Hash Sum mismatch, the set up is the aforementioned as the one in the previous error.
W:Failed to fetch bzip2:/var/lib/apt/lists/partial/in.archive.ubuntu.com_ubuntu_dists_oneiric_restricted_binary-i386_Packages Hash Sum mismatch, W:Failed to fetch bzip2:/var/lib/apt/lists/partial/in.archive.ubuntu.com_ubuntu_dists_oneiric_multiverse_binary-i386_Packages Hash Sum mismatch, E:Some index files failed to download. They accept been ignored, or one-time ones used instead
The error occurs possibly because of a mismatched metadata enshroud between the server and your arrangement. You can utilize the following commands to set up information technology:
sudo rm -rf /var/lib/apt/lists/* sudo apt update Fault 3: Failed to fetch with error 404 not found
If you try adding a PPA repository that is non available for your electric current Ubuntu version, you'll encounter that information technology throws a 404 non institute error.
W: Failed to fetch http://ppa.launchpad.net/venerix/pkg/ubuntu/dists/raring/master/binary-i386/Packages 404 Not Found E: Some index files failed to download. They have been ignored, or sometime ones used instead.
You added a PPA hoping to install an awarding but information technology is not available for your Ubuntu version and you are now stuck with the update error. This is why you should check beforehand if a PPA is available for your Ubuntu version or not. I have discussed how to check the PPA availability in the detailed PPA guide.
Anyway, the gear up hither is that you lot remove the troublesome PPA from your list of repositories. Note the PPA name from the error bulletin. Get to Software & Updates tool:
In here, motility to Other Software tab and look for that PPA. Uncheck the box to remove the PPA from your system.
Your software list will be updated when you do that. Now if yous run the update once again, you shouldn't see the fault.
Error 4: Failed to download package files error
A like error isfailed to download package files errorsimilar this:
In this case, a newer version of the software is available but it'south not propagated to all the mirrors. If you are non using a mirror, easily fixed by irresolute the software sources to Chief server. Please read this article for more details on failed to download package fault.
Go to Software & Updates and in there changed the download server to Main server:
Error 5: GPG mistake: The following signatures couldn't be verified
Adding a PPA may likewise issue in the following GPG error: The following signatures couldn't be verified when y'all try to run an update in terminal:
West: 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 you need to do is to fetch this public key in the arrangement. Go the fundamental number from the message. In the above message, the central is 68980A0EA10B4DE8.
This central can be used in the following mode:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68980A0EA10B4DE8
Once the key has been added, run the update once again and information technology should exist fine.
Error 6: BADSIG mistake
Another signature related Ubuntu update error is BADSIG error which looks something similar this:
W: A error occurred during the signature verification. The repository is non updated and the previous alphabetize 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 post-obit signatures were invalid: BADSIG 4C1CBC1B69B0E2F4 Launchpad PPA for Jonathan French W: Failed to fetch http://extras.ubuntu.com/ubuntu/dists/precise/Release
All the repositories are signed with the GPG and for some reason, your system finds them invalid. You'll need to update the signature keys. The easiest way to do that is by regenerating the apt packages list (with their signature keys) and information technology should take the correct fundamental.
Utilise the following commands one by one in the terminal:
cd /var/lib/apt sudo mv lists oldlist sudo mkdir -p lists/fractional sudo apt-get clean sudo apt-get update
Error 7: Partial upgrade error
Running updates in terminal may throw this fractional upgrade fault:
Not all updates can be installed
Run a partial upgrade, to install as many updates equally possible
Run the following command in terminal to fix this error:
sudo apt-get install -f
Error eight: Could not get lock /var/enshroud/apt/archives/lock
This mistake happens when some other program is using APT. Suppose you lot are installing some thing in Ubuntu Software Center and at the aforementioned time, trying to run apt in terminal.
Due east: Could not get lock /var/cache/apt/archives/lock – open (11: Resource temporarily unavailable)
Due east: Unable to lock directory /var/cache/apt/archives/
Check if some other plan might be using apt. It could be a command running terminal, Software Center, Software Updater, Software & Updates or any other software that deals with installing and removing applications.
If you tin can shut other such programs, close them. If at that place is a process in progress, expect for it to finish.
If you cannot find whatever such programs, apply the following command to kill all such running processes:
sudo killall apt apt-get
This is a tricky problem and if the trouble still persists, delight read this detailed tutorial on fixing the unable to lock the administration directory error in Ubuntu.
Any other update error you encountered?
That compiles the list of frequent Ubuntu update errors yous may encounter. I hope this helps you to go rid of these errors.
Have you encountered whatsoever other update error in Ubuntu recently that hasn't been covered here? Practise mention information technology in comments and I'll try to practise a quick tutorial on it.
Source: https://itsfoss.com/ubuntu-update-error/
0 Response to "There Was an Error While Updating: Login Error. Please Login Again. (-3333)"
Post a Comment