84

See https://discourse.ubuntu.com/t/focal-fossa-20-04-1-lts-point-release-status-tracking/17604 for the current status. On 25 September 2020, the final upgrade-blocking bug was closed. If you are reading this on 25-27 September, just be patient while your local mirror catches up.


57

I just ran into this problem on Pop!_OS 18.04, trying to upgrade to 18.10, and it turns out that the problem lay in the symlink for /usr/bin/python and not for /usr/bin/python3. I had had /usr/bin/python3.6 configured as an alternative for python (not python3), and when I changed this, then I could run do-release-upgrade as expected. I wish the error ...


53

What worked for me was removing any broken packages, as they were preventing the upgrade. First find out which packages are broken: grep Broken /var/log/dist-upgrade/apt.log Then remove them: sudo apt-get remove <packages to remove> Some might be reinstalled during the upgrade, others you may have to reinstall yourself.


45

Important Security Notice This answer will disable an critical security feature in Ubuntu. It will stop Ubuntu checking packages are the the same as they were when they were built. This could mean your updates are compromised or corrupt. This could mean there's just a bug in the way Ubuntu's release upgrades are handled. I'm not saying you ...


39

do-release-upgrade is part of the package “update-manager-core”. The script seems to determine which release you are going to upgrade to, try to find out if it’s supported or not and complain about the latter. – If it’s convinced to work, it downloads the release-specific UpgradeTool and runs it. Part of the “update-manager-core” package is the file /etc/...


39

This is an issue that has appeared before: 4 years ago when upgrading from 12.04 LTS (Precise Pangolin) to 14.04.1 LTS (Trusty Tahr): Why is "No new release found" when upgrading from a LTS to the next? It looks like a similar issue exists for the upgrade from 14.04 LTS (Trusty Tahr) to 16.04.1 LTS (Xenial Xerus) with the relevant update log not ...


37

After your system fails to upgrade, check the file /var/log/dist-upgrade/main.log I found the line: 2013-10-17 15:00:30,543 ERROR Dist-upgrade failed: 'The package 'xubuntu-desktop' is marked for removal but it is in the removal blacklist.' I manually removed xubuntu-desktop. The upgrade then continued without issue.


34

It looks like the culprit is /etc/update-motd.d/91-release-upgrade This calls /usr/lib/ubuntu-release-upgrader/release-upgrade-motd This file checks for the file /var/lib/ubuntu-release-upgrader/release-upgrade-available If that exists, it goes in the motd. If it doesn't, it calls /usr/lib/ubuntu-release-upgrader/check-new-release. That last command ...


30

You need to use the default Python 3 version for 16.04. That's 3.5, not 3.6. So run: sudo ln -sf /usr/bin/python3.5 /usr/bin/python3 If that doesn't work, try reinstalling the python3 package. sudo apt-get install --reinstall python3 By the way, update-alternatives --display python3 should give you update-alternatives: error: no alternatives for python3. ...


26

No. Ubuntu does have LTS→LTS upgrades, allowing you to skip intermediate non-LTS releases... But you can't skip intermediate LTS releases. You have to go via 16.04. Unless you want to do a fresh install of 18.04 on release. I should also note that the LTS upgrade pathways are usually only available some time after the main release. So don't expect to be ...


23

Test this: Open a terminal (press Ctrl+Alt+T). Run this: sudo -i apt-get update apt-get autoremove apt-get clean UNUSCONF=$(dpkg -l|grep "^rc" | awk '{print $2}') apt-get remove --purge $UNUSCONF NEWKERNEL=$(uname -r|sed 's/-*[a-z]//g'|sed 's/-386//g') ADDKERNEL="linux-(image|headers|ubuntu-modules|restricted-modules)" METAKERNEL=&...


23

I found this note in How To Upgrade Ubuntu To 20.04 LTS Focal Fossa - LinuxConfig.org PLEASE NOTE Upgrades from 19.10 will not be enabled until a few days after 20.04's release. Upgrades from 18.04 LTS will not be enabled until a few days after the 20.04.1 release expected in late July 2020. There are no offline upgrade options for Ubuntu Desktop and ...


20

You seem to be running a 32-bit version of Ubuntu, as evidenced by: There will not be any further Ubuntu releases for this system's 'i386' architecture. That's correct. 32-bit desktops have been dropped from future releases, including 20.04. There were simply too few 32-bit desktop contributors and testers. Your current 32-bit Ubuntu 18.04 will be ...


19

I had the exact same error. The solution I found in order to upgrade the remaining last 2 packages was: sudo su - cd /boot/efi/EFI mv ubuntu ubuntu-old apt install -f mv ubuntu-old ubuntu update-grub2 exit I hope it helps.


18

You have to mount your ESP. This should work with: sudo mount /boot/efi If you get an error message like mount: can't find /boot/efi in /etc/fstab you have to add a line to your /etc/fstab e.g. UUID=XXXX-XXXX /boot/efi vfat umask=0077 0 1 replace the XXXX-XXXX with the UID of your ESP (e.g. from the output of blkid /dev/sdxX or ...


14

To fix your first problem run this in a terminal: sudo rm /etc/apt/sources.list.d/*.disable (An older version of the package management tool left these files when you disabled the PPAs. Removing them is pretty safe) Your second problem comes from and old Karmic repository. To find out which one run this in a terminal: cd /etc/apt grep -rw karmic * Once ...


14

You are viewing the output of diff old-conf-file new-conf-file | more. Simply press Q to exit.


13

First, advice to others who want to install a beta version, besides the classic "backup your data": if update-manager -d fails with too many errors and does not rewind what it has done, do not force a restart. close update-manager, if necessary, kill the process. do an apt-get -f install, followed by apt full-upgrade. Repeat with apt update and apt full-...


13

important production system I would not upgrade a system like that. I would install 16.04 on another machine, copy the live data over to that machine. Test, test some more. And then make that machine the production server. And you can redo this with 18.04 with the current 14.04 server. Why take risks at all?


13

It seems like there is an issue about certificates: result of meta-release download: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:841)> As a workaround, I edited the file /usr/lib/python3/dist-packages/UpdateManager/Core/MetaRelease.py and added these lines to the beginning: import ssl ssl....


12

Your original guess was right. 15.04 is supported through 2016-02-04, so do-release-upgrade is trying to upgrade you to the next supported release compared to the one you have. Here's the description of normal upgrade prompting mode from /etc/update-manager/release-upgrades: Check to see if a new release is available. If more than one new release is ...


12

If do-release-upgrade fails, you might need to edit the release-updates file. Open that file with a text editor (e.g. nano) nano /etc/update-manager/release-upgrades Edit the last line to say: Prompt=normal Then run do-release-upgrade (without the -d flag) When the upgrade is complete, edit that line again to say Prompt=lts


12

http://ubuntu-news.org/2020/01/23/ubuntu-19-04-disco-dingo-end-of-life-reached-on-january-23-2020/ https://lubuntu.me/lubuntu-19-04-end-of-life-and-current-support-statuses/ From the Lubuntu EOL message is Lubuntu 19.04 End of Life and Current Support Statuses Lubuntu 19.04 (Disco Dingo) will reach End of Life on Thursday, January 23, 2020. This ...


12

sequence from 18.04 to 20.04 sudo apt update sudo apt upgrade sudo apt dist-upgrade sudo apt autoremove sudo do-release-upgrade -d -f DistUpgradeViewGtk3 Follow onscreen instruction. Good luck!


11

Neither. You do not need to reinstall Lubuntu 18.04 or start over with Ubuntu 18.04 LTS, because you can upgrade to Lubuntu 19.10, which is very easy, and fully supported. This is a general solution for all users of Ubuntu, Lubuntu, Kubuntu, and other supported Ubuntu flavours. sudo apt update && sudo apt dist-upgrade sudo apt install update-...


10

Try executing: grep ERROR /var/log/dist-upgrade/main.log Hopefully this will show you the names of conflicting packages. For me it was (I broken long line to be easier to read): 2014-10-25 18:15:05,915 ERROR Dist-upgrade failed: 'The package 'postgresql-9.3-postgis-2.1' is marked for removal but it is in the removal blacklist. postgresql-9.3-...


10

No. There never will be another Ubuntu that is 32-bit. You will need to switch to an alternative. Some of the official flavors intend to keep 32-bit in their arsenal. But I would assume they will stick to LTS for 32-bit. 3 examples: Budgie. 18.04 is 64 and 32. 19.04 is 64 only. No 18.10 download. Xubuntu 18.04 is 64 and 32. 19.04 is 64 only. No 18.10 ...


10

I was also experiencing the same issue. However, when I ran the usual upgrade commands (sudo apt upgrade, sudo apt full-upgrade, sudo apt-get dist-upgrade), they were all reporting that there are no packages to upgrade and no held packages: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. In the end, I copied the file /usr/bin/do-release-...


9

I wrote a script to do this, for my own upgrade of multiple machines to Ubuntu 14.04 "trusty". It is called 'apt-get-other-release'. Simple use: $ sudo apt-get-other-release -t trusty [ a long time passes as it downloads stuff ] $ sudo apt-get-other-release -U [ it prepares the system for upgrade -- this is quick ] $ sudo do-release-upgrade # or ...


9

There won't be any special notifications for this. Just do the standard updates. sudo apt-get update sudo apt-get dist-upgrade.


Only top voted, non community-wiki answers of a minimum length are eligible