How to Upgrade Linux Mint 19.3 to Mint 20: A Careful Migration Guide

 

Conceptual illustration of a Linux Mint upgrade
Conceptual illustration of a Linux Mint upgrade.

On July 9, 2020, the Linux Mint team announced that users could upgrade the 64-bit edition of Linux Mint 19.3 to Linux Mint 20. The process moves the system to a new package base and can preserve an existing installation, but it deserves more preparation than a routine software update.

An upgrade changes repositories, replaces many packages and may expose conflicts with third-party software or hardware drivers. A successful migration begins before the first upgrade command: verify the current system, make a separate backup, create a system snapshot and decide how you will recover if the machine cannot boot.

This guide explains the upgrade path announced in July 2020. It is written for readers comfortable using a terminal and reading package-management output. If that is unfamiliar, a clean installation on a spare disk or help from an experienced Linux user may be a better choice.

First decide whether you need to upgrade

Linux Mint 20 “Ulyana” offers a newer Ubuntu-based foundation and improvements to the desktop, file sharing and hardware support. The previous long-term-support release did not stop functioning when the new one arrived. A working, supported system may be preferable to a rushed migration on the day a major upgrade becomes available. For a broader look at choosing and using Linux on personal computers, see CIALU.NET’s earlier article Happy again, with Linux.

Ask what the computer does and which parts of the workflow are difficult to replace. A home laptop used for browsing and documents may tolerate more experimentation than a production workstation with specialized drivers, audio plugins, virtual machines or business software.

The Linux Mint team’s July announcement emphasizes patience, current updates and snapshots. That advice reflects the nature of a distribution upgrade: it affects a large set of interdependent packages, not just the visual appearance of the desktop.

Upgrade or fresh installation?

An in-place upgrade updates the existing operating system and attempts to retain installed software and configuration. It can save time if the machine is clean and well maintained, but old repositories, locally modified files and obsolete packages can complicate the process.

A fresh installation starts with a new system and then restores data and applications from backups. It can remove accumulated complexity, but it requires more work to rebuild the environment. It also carries the risk of selecting the wrong disk or partition during installation.

Neither option is a substitute for a backup. Choose based on your skills, available time, the machine’s configuration and the reliability of your recovery plan.

Check the starting point

The official upgrade guide describes the path from Mint 19.3 to Mint 20. It requires the 64-bit version of Mint 19.3 and experience with APT and the command line. A 32-bit installation cannot be upgraded to Mint 20 through this path.

To check the installed architecture, open a terminal and run:

dpkg --print-architecture

The guide identifies amd64 as the supported 64-bit architecture for this upgrade and i386 as a 32-bit installation. The output describes the installed system architecture; a 64-bit-capable processor running a 32-bit operating system does not turn that installation into a 64-bit one.

Check the current Mint version in the system information tools as well. If you are running an earlier release, consult the project’s documented upgrade paths rather than assuming you can skip directly to the target version.

  • Starting version: Linux Mint 19.3, 64-bit.
  • Skills: ability to read terminal output and understand package changes.
  • Time: a window long enough to download, upgrade, reboot and test.
  • Recovery: a separate data backup and a usable system snapshot.

Back up your personal data separately

Copy documents, photographs, videos, project folders and other irreplaceable files to a separate device or trusted backup service. Include items that are easy to overlook: browser bookmarks, email archives, password-manager recovery information, application profiles and configuration files needed for specialized work.

A separate backup protects against failures that an operating-system snapshot may not cover. A snapshot stored on the same physical disk may be unavailable if the disk fails. A snapshot’s default configuration may also exclude personal files. Check what is actually included rather than assuming every item is protected.

Test the backup. Open several files from the destination, confirm that the expected folders are present and make sure the recovery credentials are available. A backup process that runs without an error message is reassuring, but restoration is the meaningful test.

If the computer uses encryption, understand how to unlock the backup and the installed system from a recovery environment. Keep recovery information separate from the computer being upgraded. Do not leave the only copy of an encryption key on a disk you are about to reformat.

Conceptual illustration of a Linux user preparing a backup
Conceptual illustration of a Linux user preparing a backup.

Update the existing system

Use Update Manager to refresh the package list and install available updates for the current release. The official guide recommends continuing until the manager reports that the system is current, then rebooting. This reduces the chance of beginning a major upgrade with unresolved updates or an old running kernel.

After rebooting, confirm that ordinary operations still work. Check network access, login and the applications needed to complete the upgrade. A pre-existing package problem should be understood before adding the complexity of a new distribution base.

Make sure the computer has a reliable power supply and a stable network connection. A laptop should be connected to power. If you are working remotely, consider how you would recover the machine if the network or graphical session became unavailable.

Create and understand a system snapshot

Mint’s guide recommends creating a snapshot with Timeshift before upgrading. A snapshot records system state so that it can be restored if the upgrade breaks the installation. Choose a suitable destination and make sure the snapshot completes successfully before proceeding.

Understand the limits of the snapshot. Timeshift is designed primarily for system restoration, and its treatment of personal files depends on configuration. A separate backup remains necessary. A snapshot cannot be useful if the storage containing it is unavailable or if you do not know how to start the recovery environment.

Prepare a live USB that can boot the machine and provide access to recovery tools. Test that the computer can start from it before changing the installed system. If secure boot, firmware settings or disk encryption complicate access, resolve those questions while the existing installation still works.

The official guide recommends another snapshot after dealing with third-party packages. That gives you a record of a cleaner pre-upgrade state as well as the earlier snapshot. Label snapshots clearly so you know which state each one represents.

Conceptual illustration of a Linux software update
Conceptual illustration of a Linux software update.

Review PPAs and third-party repositories

Additional repositories can supply useful software, but they can also introduce packages newer than or incompatible with the target release. A package manager may be unable to satisfy dependencies if a third-party package expects libraries that differ from those in Mint 20.

Use Software Sources to review additional repositories and personal package archives. The Mint guide recommends disabling them and using the maintenance options to downgrade or remove foreign packages before upgrading. It describes this as optional but strongly recommended.

Do not remove packages blindly. A “foreign” package may provide a tool or driver you need. Record the package name, understand what will be removed or downgraded and check whether a supported version is available for the new release. If a repository contains essential software, investigate its compatibility before starting.

After changing sources, refresh the package cache, reboot if appropriate and create a new snapshot. If you decide to leave a third-party package in place, recognize that it may complicate the upgrade and have a plan for restoring the previous state.

Install the upgrade tool

The official instructions use the mintupgrade utility. On a prepared Mint 19.3 system, the documented installation command is:

apt install mintupgrade

Read the output and resolve errors before proceeding. If the package cannot be found, the problem may involve stale package information or a mirror that has not synchronized. The project’s announcement notes that switching back to the default repositories and refreshing the cache can help in that situation.

Do not respond to a package error by copying an arbitrary repair command from an unrelated forum post. Identify the actual error, consult the official documentation and seek help with the exact version and output if necessary.

Simulate before changing the system

Run the documented check:

mintupgrade check

The check simulates the upgrade and reports packages that would be installed, upgraded, removed or held back. It temporarily uses the target repositories to calculate the proposed changes and then restores the original sources. The simulation is designed to show the impact before the actual upgrade.

Read the proposed removals carefully. A package may be obsolete or replaced, but it may also be a tool you rely on. Investigate unexpected removals, unresolved dependencies and held packages before continuing. The official guide recommends repeating the check until you are satisfied with the result.

A successful simulation is useful, but it is not a promise that every driver, device and application will work after the upgrade. The check cannot reproduce every real-world condition or anticipate a power failure. That is why the backup and recovery plan remain essential.

If the check fails

Stop and preserve the error output. The guide notes that if the check fails partway through, mintupgrade restore-sources can restore the original APT source configuration. Follow the official instructions and verify the result before attempting other changes.

Common areas to investigate include disabled or conflicting repositories, packages installed from outside the distribution and incomplete earlier updates. The exact remedy depends on the error. Removing large groups of packages without understanding their role can turn a recoverable conflict into a bigger problem.

Ask for help with the complete error, Mint version and relevant repository information, while removing passwords or other private data. A precise report is more useful than saying only that “the upgrade does not work.”

Conceptual illustration of a user checking a backup
Conceptual illustration of a user checking a backup.

Download and apply the upgrade

Once the check is satisfactory, the official guide separates downloading from applying the changes:

mintupgrade download

This stage downloads the packages needed for the upgrade. It does not by itself perform the complete transition. Confirm that downloads finish successfully and that sufficient space remains before moving on.

The next command applies the upgrade:

mintupgrade upgrade

This is the consequential step. The Mint guide describes it as non-reversible through a simple downgrade; returning to the earlier system requires restoring a snapshot or reinstalling. Do not interrupt the process, and be prepared to read prompts and respond where required.

During a major package transition, the system may ask what to do with locally modified configuration files. The correct choice depends on whether you intentionally changed the file and whether the new package requires a different configuration. Keep a record of decisions and do not assume that accepting every default is always right for a customized machine.

Reboot and verify the result

After the upgrade completes, follow the guide’s remaining steps, including checking for foreign packages that need to be downgraded. Reboot and confirm that the computer starts normally. Keep the recovery USB and backup available until you are satisfied with the result.

Test the functions that matter to your work. A successful login is only the first check. Confirm that Wi-Fi or Ethernet works, sound plays, the display uses the expected resolution, printing is available and external drives mount correctly.

Open representative documents and projects. Test a browser, email client, development environment or creative application as appropriate. If you use a discrete GPU, verify the active driver and the behavior of the applications that need it.

Check the backup process again. Paths, mounted drives or application settings may have changed. A system that appears healthy today should still be recoverable after a later mistake or hardware failure.

Laptop with code on screen and red backlit keyboard
A laptop used for programming. Photo: Danny Meneses / Pexels. Photo source · License

What to do if something is wrong

Begin by describing the symptom precisely. Does the machine fail to boot, stop at login, lose networking or open one application incorrectly? A specific symptom helps narrow the problem and avoids unnecessary changes to working components.

Use the live environment if the installed system cannot start, and consult the project’s recovery documentation. If you need to restore a snapshot, understand which snapshot you are selecting and what it will replace. Preserve recent personal files separately before restoring a system state.

Do not repeatedly run destructive repair commands without understanding their effect. Disk formatting, forced package removal and changes to boot configuration can make recovery harder. When in doubt, stop, keep the error message and seek informed help.

A measured approach to a major upgrade

Mint 20 offers a newer foundation, but an upgrade is successful only if the user’s actual work continues and the system remains recoverable. Preparation, a separate backup, a readable simulation and a deliberate post-upgrade test are more valuable than rushing through a sequence of commands.

The July 2020 upgrade path gives experienced Mint 19.3 users a way to move forward without necessarily reinstalling. Follow the official instructions for the specific release, take time to understand proposed changes and keep the option to restore your system if the result is not satisfactory.

Laptop screen displaying source code
Source code on a laptop. Photo: StockSnap / Pixabay. Photo source · License

Sources