I want to upgrade from Kubuntu 20.04 to 21.04. I have changed /etc/update-manager/release-upgrades so that Prompt=normal. Running pkexec do-release-upgrade -m desktop -f DistUpgradeViewKDE I get the option to upgrade to 21.10.  Also, sudo do-release-upgrade -m desktop [sudo] password for cip:  Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B]                                                                                                                                     Get:2 Upgrade tool [1 340 kB]                                                                                                                                            Fetched 1 341 kB in 0s (0 B/s)                                                                                                                                           authenticate 'groovy.tar.gz' against 'groovy.tar.gz.gpg'  extracting 'groovy.tar.gz'  I guess that should say hirsute instead of groovy.  How to upgrade to latest 21.04 directly?
3113
I am currently using Ubuntu 10.04. I know there is a 10.10 release, but can I upgrade directly to 11.04? Could you walk me through the steps please?
30485
When I do upgrade it gets stuck here:  user@plato:~# sudo apt-get upgrade Reading package lists... Done Building dependency tree        Reading state information... Done Calculating upgrade... Done The following packages will be upgraded:   bind9-host coreutils cpio curl dnsutils libbind9-90 libc-bin libc-dev-bin   libc6 libc6-dev libcgmanager0 libcurl3 libcurl3-gnutls libdns100   libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libisc95 libisccc90   libisccfg90 libjasper1 liblwres90 libplymouth2 libsepol1 libssl-dev   libssl-doc libssl1.0.0 linux-libc-dev mime-support multiarch-support ntp   ntpdate openssl plymouth plymouth-theme-ubuntu-text python3-distupgrade   ubuntu-release-upgrader-core unzip 39 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 16.0 MB of archives. After this operation, 12.3 kB of additional disk space will be used. Do you want to continue? [Y/n] y 0% [Connecting to us.archive.ubuntu.com (2001:67c:1562::15)] ░   When I do update it gets stuck here:  user@plato:~# apt-get update 0% [Connecting to us.archive.ubuntu.com (2001:67c:1562::14)] [Connecting to sec░   I'm able to ping us.archive.ubuntu.com just fine:  user@plato:~# ping us.archive.ubuntu.com PING us.archive.ubuntu.com (91.189.91.23) 56(84) bytes of data. 64 bytes from economy.canonical.com (91.189.91.23): icmp_seq=1 ttl=54 time=81.5 ms 64 bytes from economy.canonical.com (91.189.91.23): icmp_seq=2 ttl=54 time=81.5 ms 64 bytes from economy.canonical.com (91.189.91.23): icmp_seq=3 ttl=54 time=81.5 ms 64 bytes from economy.canonical.com (91.189.91.23): icmp_seq=4 ttl=54 time=81.4 ms ^C --- us.archive.ubuntu.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 81.425/81.528/81.582/0.355 ms   What can i do to fix this?    What I have tried so far.  I've tried following directions on this blog:   To force apt-get to use IPv4 exclusively   Create a file in /etc/apt/apt.conf.d/99force-ipv4 Add this line to newly created file Acquire::ForceIPv4 false; Apt-get will now use IPv4 exclusively
9631
I am using Ubuntu 12.10.  Please outline the different ways I can upgrade to 13.04.
123011
When I run sudo apt-get update on my fully updated Ubuntu 16.04.6 LTS I get the following errors about Google repositories:  $ sudo apt update ... Err:20 http://dl.google.com/linux/earth/deb stable Release.gpg   The following signatures were invalid: KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520 Get:21 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB] Err:13 http://dl.google.com/linux/chrome/deb stable Release.gpg    The following signatures were invalid: KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520 ... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/earth/deb stable Release: The following signatures were invalid: KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures were invalid: KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520 W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg  The following signatures were invalid: KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520 W: Failed to fetch http://dl.google.com/linux/earth/deb/dists/stable/Release.gpg  The following signatures were invalid: KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520  KEYEXPIRED 1555048520 W: Some index files failed to download. They have been ignored, or old ones used instead.   The apt-key list returns:  pub   1024D/7FAC5991 2007-03-08 uid                  Google, Inc. Linux Package Signing Key &lt;linux-packages-keymaster@google.com&gt; sub   2048g/C07CB649 2007-03-08  pub   4096R/D38B4796 2016-04-12 uid                  Google Inc. (Linux Packages Signing Authority) &lt;linux-packages-keymaster@google.com&gt; sub   4096R/997C215E 2017-01-24 [expires: 2020-01-24]    Removing Google keys and packages with   sudo apt-key del D38B4796 sudo apt-key del 7FAC5991 sudo apt purge google-chrome-stable  sudo apt purge google-earth-pro-stable sudo apt purge google-earth-stable   and reinstalling packages with   cd ~/Downloads wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb sudo apt-get install --reinstall ./google-chrome-stable_current_amd64.deb  wget https://dl.google.com/dl/earth/client/current/google-earth-pro-stable_current_amd64.deb sudo apt-get install --reinstall ./google-earth-pro-stable_current_amd64.deb   does not help.  Executing command from  :  wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -   does not help.  How should I fix it?  What else I did: 1. sent feedback from Google Chrome with Help → Report an Issue. 2. sent feedback from Google Earth using Help → Send feedback. 3. created thread on
100260
I typed  sudo apt-get upgrade   And I got this  $ sudo apt-get upgrade Reading package lists... Done Building dependency tree        Reading state information... Done Calculating upgrade... Done The following packages will be upgraded:   bind9-host dnsutils google-chrome-stable libbind9-161 libdns-export1104   libdns1104 libirs161 libisc-export1100 libisc1100 libisccc161 libisccfg163   liblwres161 python3-distupgrade ubuntu-release-upgrader-core   ubuntu-release-upgrader-gtk 15 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/61.1 MB of archives. After this operation, 1,769 kB of additional disk space will be used. Do you want to continue? [Y/n]  dpkg: unrecoverable fatal error, aborting:  unknown system group 'smmsp' in statoverride file; the system group got removed before the override, which is most probably a packaging bug, to recover you can remove the override manually with dpkg-statoverride E: Sub-process /usr/bin/dpkg returned an error code (2)   Can any one throw any light on this?
36227
I would like to upgrade my main system to 16.04, but I work on projects that require OpenJDK 7.   Apparently it is not available from a trivial apt-get install openjdk-7-jdk. Only versions 8 and 9 are listed in the repository.  Can anyone point me to instructions on how to install it?
37975
I've understood that when I run the Software Updater GUI program, or when I execute do-release-upgrade on the command line, it should offer to upgrade to the latest LTS release if (1) I've got the release update behaviour set to lts, and (2) if the first point release of a newer LTS release is available. I have a couple of machines running the Xubuntu LTS release 18.04. The contents of file etc/update-manager/release-upgrades on all these machines is [DEFAULT] Prompt=lts  That satisfies condition (1). Also, it seems that Xubuntu 20.04.1 is already released, satisfying condition (2). However, neither do-release-upgrade nor the Software Updater offers to upgrade to that release. Why? Edited to add: It seems this question is a duplicate of .
13138
Attempting to upgrade testing/stretch Debian Linux:  $ sudo apt update  Ign:1 http://dl.google.com/linux/talkplugin/deb stable InRelease Hit:2 http://dl.google.com/linux/talkplugin/deb stable Release                                                                    ... Get:25 http://mirror.vorboss.net/debian unstable/main i386 Packages 2016-03-25-1456.28.pdiff [15.0 kB]              Fetched 686 kB in 7s (89.5 kB/s)                                                                                                                                                         Reading package lists... Done W: gpgv:/var/lib/apt/lists/dl.google.com_linux_talkplugin_deb_dists_stable_Release.gpg: The repository is insufficiently signed by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 (weak digest) W: gpgv:/var/lib/apt/lists/deb.opera.com_opera_dists_stable_InRelease: The repository is insufficiently signed by key 419D0ACF314E8E993F7F92E563F7D4AFF6D61D45 (weak digest) W: Failed to fetch http://dl.google.com/linux/talkplugin/deb/dists/stable/Release  No Hash entry in Release file /var/lib/apt/lists/dl.google.com_linux_talkplugin_deb_dists_stable_Release, which is considered strong enough for security purposes E: Some index files failed to download. They have been ignored, or old ones used instead.  What's wrong? How to fix it?
420
I have been trying to install the latest version of java-8. However, I found out that the  due to changes in the java licence.  How should I update my java to 8.0_201 or 8.0_211 now?  Thanks!
25029
I just finished backing up my system and when I try to upgrade to Utopic Unicorn, I get the error "Cannot Calculate the upgrades." I ran the upgrade by sudo apt-get dist-upgrade, sudo do-release-upgrade after the GUI method failed, they all gave the same error.  The feedback gives some recommendations:  This can be caused by:  * Upgrading to a pre-release version of Ubuntu  * Running the current pre-release version of Ubuntu  * Unofficial software packages not provided by Ubuntu    I am not upgrading to a pre-release version nor coming from one, I'm going from Ubuntu 14.04 LTS to 14.10. I have no broken packages and I have unchecked all my non-official software sources in the 'Software &amp; Updates' manager.  My guess left is the Unofficial software packages not provided by Ubuntu. If anyone could give any help as to how to check for unofficial packages using Synaptic or another, my appreciation.  Are there any other factors that may be causing this error and how would I go about checking/fixing those?  Thanks.  Edit: I have no broken or held packages. Everything is up-to-date, and restarting everything or anything has no effect.
117228
I downloaded the .tar.gz version of VS Code for Ubuntu (64-bit) and have been able to run it smoothly for some time. Some extensions have been installed too.  How can I efficiently update this VS Code installation? One thing I can think of is to just download the new .tar.gz archive and extract to the same location, just keeping the old "extensions" folder.   If I use the .deb version, would the same process be needed? Would I download the new .deb every time there is an update?
17708
I just upgraded from Ubuntu 15.04 64-bit to Ubuntu 15.10 64-bit. I read that 15.10 was using the 4.1 or 4.2 kernel, but I noticed that my kernel didn't upgrade.  When I type in the terminal uname -r, I get 3.19.0-18-generic  Same thing in GRUB: the only kernel I can choose is 3.19.0-18  Can someone explain how to upgrade the kernel?
51958
The update from Trusty to Xenial is officially available via the software updater. After updating all packages, upgrading through the software updater yields:  Fetching the upgrade failed. There may be a network problem.   Doing a sudo do-release-upgrade yields:      Checking for a new Ubuntu release Err Upgrade tool signature                                                        403  Sorry, not allowed to fetch that type of file: xenial.tar.gz.gpg         Err Upgrade tool                                                                  403  Sorry, not allowed to fetch that type of file: xenial.tar.gz             Fetched 0 B in 0s (0 B/s)                                                       WARNING:root:file 'xenial.tar.gz.gpg' missing Failed to fetch Fetching the upgrade failed. There may be a network problem.
96856
I'm on an old Ubuntu version (Ubuntu 6.06.2 LTS Server) which isn't really supported any more. So the automatic updates don't work. I have ISPConfig installed to manage a few web sites.  What's the best course of action? I'd like to upgrade to something current, but I can't figure out how to go about doing this, given that the apt-get scripts don't really work any longer.
31504
I can't update 12.04 LTS. The Update Manager shows this:  CD/DVD 'Ubuntu 12.04 LTS _Precise Pangolin_ - Release i386 (20120423)' is required Please insert the above CD/DVD into the drive '/media/cdrom/' to install software packages from it.   The image I downloaded and burned to CD is from  the PC (Intel x86) desktop CD version. I burned many CDs but the result is the same.
14740
I can't find any documentation on upgrading 16.04 to 16.04.1.  I'm assuming having all the package updates does it, but Details is still reporting 16.04 and there is still a 'developer options' tab in Software &amp; Updates, implying I'm still in some experimental release.
57787
When I upgrade from one version of Ubuntu to the next, the upgrade tool rightly disables all my PPAs, so that software compiled for or otherwise tied to the old version of Ubuntu does not interfere with the new version that I just upgraded to.  Is there any way to automatically re-enable and update any PPAs that provide packages for the new version of Ubuntu? For example, suppose I'm currently running Maverick, and I have two PPAs enabled, "foo" and "bar". Suppose that "foo" provides packages for both Maverick and Natty, while "bar" provides packages for Natty only. Is there a tool I could run after updating to Natty that would re-enable my "foo" PPA and update it to point to the Natty packages, while leaving the "bar" PPA disabled?