Ubuntu 26.04 LTS: Read the Upgrade Path, Not Just the Feature List

Ubuntu 26.04 LTS “Resolute Raccoon” was released on 23 April 2026. The most important improvement for an upgrader may be how Canonical now documents the release: the official notes explicitly separate the two-year journey from Ubuntu 24.04 LTS from the smaller step after Ubuntu 25.10 1.

That distinction prevents a common reading error. A feature introduced in an interim release can still be new to an LTS user even if it was not developed in the final six months before 26.04.

Choose the correct starting column

The LTS summary collects the larger desktop, security, application, and platform changes accumulated since 24.04 2. The incremental page avoids presenting that entire two-year set as if it landed only after 25.10.

Confirm the machine’s actual starting point

Do not infer the release from the wallpaper or a remembered install date:

. /etc/os-release
printf 'release=%s codename=%s\n' "$VERSION_ID" "$VERSION_CODENAME"
uname -r

/etc/os-release identifies the operating-system image. uname -r identifies the running kernel. Those versions legitimately differ: an LTS can receive newer hardware-enablement kernels without becoming a different Ubuntu release.

Then inspect pending package work without approving an installation:

Caution: apt update uses the network and writes refreshed package indexes (and can invoke configured APT hooks). It does not install upgrades, but it is not a read-only command. Run it only on a host where refreshing metadata is an intended administrative action.

sudo apt update
apt list --upgradable 2>/dev/null
apt-mark showhold

After that refresh, apt list and apt-mark inspect the available upgrades and holds. The last command catches held packages that can complicate dependency resolution.

What changed is less important than what you use

The official LTS summary is the source of truth for the broad change set. Build an upgrade checklist from machine-specific boundaries:

• Desktop session: graphics driver, Wayland behavior, accessibility tools, extensions, remote desktop, and fractional scaling.
• Security: full-disk encryption method, TPM enrollment, Secure Boot, VPN, smart cards, and enterprise identity.
• Applications: native packages, snaps, third-party repositories, locally installed binaries, and language runtimes.
• Server roles: database versions, web server modules, container runtime, firewall rules, and maintenance-window expectations.

This turns a long release note into a finite test plan. A feature that does not touch the machine is interesting; a known issue in its storage or login path is decisive.

Preflight before the upgrader

Canonical’s desktop procedure includes making the current installation healthy, backing up important data, and running the supported release upgrader 3. Add four practical checks:

df -h /
df -h /boot /boot/efi 2>/dev/null
systemctl --failed --no-pager
findmnt -no SOURCE,FSTYPE,OPTIONS /

These are read-only. They expose low space, already-failed services, and the root-filesystem boundary before an upgrade changes thousands of packages.

Also record third-party package sources:

find /etc/apt/sources.list.d -maxdepth 1 -type f \
  \( -name '*.list' -o -name '*.sources' \) -print
grep -hsE '^[[:space:]]*(deb |Types:|URIs:|Suites:)' \
  /etc/apt/sources.list \
  /etc/apt/sources.list.d/*.list \
  /etc/apt/sources.list.d/*.sources 2>/dev/null
snap list 2>/dev/null

The two APT source formats use different fields 5; inspecting only lines beginning deb misses modern deb822 .sources files. Do not paste the output publicly without checking it for private repository names. Disable or update unsupported third-party sources according to their owners’ instructions; do not blindly rewrite suite names with a global search.

Backout is part of the plan

A file backup is necessary but not always sufficient. Know how to boot an older kernel, unlock encrypted storage, reach a console if the graphical session fails, and restore the services that matter. For a VM, confirm that the snapshot mechanism is application-consistent and that someone has tested restore—not merely snapshot creation.

Ubuntu’s LTS label describes Canonical’s release and maintenance policy 4. It does not make every extension, PPA, proprietary driver, or application automatically compatible on day one.

The new documentation structure gives 26.04 upgraders a better map. Start from the release actually installed, convert only relevant changes into tests, and do not let the headline feature list replace a backup and recovery path.