Ubuntu 26.04 LTS: New Features, Key Changes, and Use Cases
April 2026 brought the latest addition to Canonical's long-term support lineup: Ubuntu 26.04 LTS, nicknamed "Resolute Raccoon." The name was chosen to honor Steve Langasek, a longtime release manager who passed away in early 2025 — and the choice reflects something genuine about this release. It doesn't hedge. Xorg is gone from the desktop. cgroup v1 is gone from the kernel. NVIDIA CUDA lands in the official package repositories for the first time. Several components have been rewritten in Rust. This is an LTS that commits to directions the Ubuntu project has been moving toward for years, rather than keeping old options around for backward compatibility.
Understanding what that means for your setup — server, workstation, container fleet, or VPS — is what this article is for. We'll walk through every major change, flag the real migration risks, and give you a clear picture of whether now is the right time to move.
Two Types of Ubuntu: Why LTS Is Different
Canonical ships Ubuntu on two tracks. Every six months, an interim release appears — 25.04, 25.10, and so on — packed with the latest upstream software. Nine months later, support ends, and you either upgrade or fall behind. These are aimed at people who want a continuously updated desktop or development environment and don't mind the churn.
LTS releases work on a completely different timeline. They appear every two years, and Canonical commits to five years of security patches and critical fixes for each one. Organizations running production infrastructure — databases, web services, build pipelines, cloud images — tend to standardize on LTS because they need predictability more than novelty. Once deployed, the system stays supported long enough to plan around it.
Ubuntu 26.04 LTS runs on that promise through April 2031. For teams that subscribe to Ubuntu Pro, the security coverage window stretches to a full decade. That 10-year horizon is what makes LTS planning meaningful — you can build on it without worrying that the OS layer will go end-of-life in the middle of a project cycle.
Hardware Requirements Before You Start
Desktop installations need a dual-core 2 GHz processor or faster, 6 GB of RAM, and at least 25 GB of disk space. The RAM figure is slightly higher than older releases — GNOME 50 on Wayland is more demanding than previous desktop configurations, particularly regarding GPU memory usage during compositing.
Server installations are considerably leaner. A minimal Ubuntu Server 26.04 configuration runs from as little as 1.5 GB of RAM and 4 GB of storage. That makes it viable for constrained cloud instances without any special tweaking. Pre-built images for cloud and virtualized environments — including VPS platforms like Serverspace — handle their own provisioning and don't require installation media at all.
Core Changes in Ubuntu 26.04 LTS
Linux Kernel 7.0
This is the first Ubuntu LTS to run the 7.x kernel series. Kernel 7.0 arrives with broader hardware compatibility for recent Intel and AMD generations, improvements to power management across CPU architectures, and measurable gains in ext4 write throughput under certain I/O patterns. The NVMe driver stack has also been updated, which benefits storage-heavy server workloads — database servers and logging pipelines in particular tend to see this kind of improvement reflected in real benchmark numbers.
One addition worth calling out specifically: Livepatch support now covers Arm-based servers. Until now, the ability to apply kernel security patches without rebooting was limited to x86-64 architecture. For teams running aarch64 production infrastructure, this finally closes that gap.
GNOME 50 and Wayland as the Only Option
Ubuntu 26.04 LTS is a turning point in the X11 story. Past releases offered a choice at the login screen — you could select "Ubuntu" (Wayland) or "Ubuntu on Xorg" (X11). That second option no longer exists. The display manager now boots into a Wayland session unconditionally. There is no fallback for users who prefer the old display server.
XWayland ships alongside, which means programs built against X11 libraries still run — they just do so inside a compatibility layer rather than talking to a native X server. For most users, the transition is invisible. The applications that cause problems are those that interact with the X server directly at a low level: some screen capture tools, certain remote desktop implementations, and a handful of GPU-intensive programs with X11-specific rendering paths.
GNOME 50 itself has matured considerably. Per-monitor scaling now handles high-DPI setups more gracefully. Screen recording can use hardware acceleration rather than burdening the CPU. Remote sessions that were previously disrupted by network drops now persist and reconnect. Small-screen support has improved enough to make Ubuntu usable on compact industrial panels and embedded touchscreens. The Orca screen reader has been substantially reworked, and a new interface option lets users reduce animations — helpful for both accessibility needs and machines with slower GPUs.
Applications: Out With the Old
Four default applications have been replaced in this cycle, and each swap is meaningful:
- Ptyxis takes over from GNOME Terminal as the default command-line environment. It runs on GTK4, renders through the GPU, and brings tab management with a full overview mode, switchable profiles, and configurable shortcuts. On identical hardware, it's noticeably more responsive than its predecessor.
- Showtime replaces the long-running Totem video player. The new player is written in Rust and built on GTK4 and libadwaita — aligned with where GNOME's application ecosystem is heading architecturally.
- Resources takes the place of GNOME System Monitor. It's a community-developed tool from the GNOME Circle program, which means it meets GNOME's quality bar without being part of the core team's direct output. It gives a clearer real-time view of what the system is actually doing.
- GIMP 3.2 replaces the 2.10 branch. The jump from 2.x to 3.x was a years-long effort to modernize GIMP's internals and UI, and 3.2 represents a fully landed version of that work.
Elsewhere: Firefox reaches version 150, LibreOffice moves from the 24.2 branch to 25.8, and Thunderbird ships as version 140, codenamed "Eclipse."
Full Disk Encryption Without a Boot Passphrase
Traditional LUKS encryption protects data at rest effectively, but it interrupts the boot process — someone (or something) has to provide the passphrase before the system continues. For physical workstations, that's fine. For unattended servers in a data center or cloud environment, it creates an operational problem: the machine can't recover from a reboot without manual intervention.
Ubuntu 26.04 addresses this with TPM-backed FDE. When the Trusted Platform Module chip is present and properly configured, it holds the encryption keys and releases them during boot automatically. The disk stays encrypted against physical theft, but reboots proceed without human input. The combination is genuinely useful for compliant-but-automated infrastructure.
Hardware limitations apply: this approach doesn't work on machines where Absolute or Computrace firmware features are active, NVMe RAID configurations may need BIOS-level adjustments first, and among out-of-tree kernel modules, only NVIDIA's driver is currently compatible. Standard setups without these edge cases work reliably.
Rust Utilities Replacing C Components
Over the past several Ubuntu releases, Canonical has been quietly replacing C-written system tools with Rust equivalents. The motivation is memory safety: Rust's ownership model eliminates whole categories of bugs — buffer overflows, null pointer dereferences, use-after-free errors — that have fueled privilege escalation vulnerabilities in system software for decades. Ubuntu 26.04 continues this push. The changes aren't visible in day-to-day use, but they reduce the exploitable surface area of the OS at a structural level rather than through patches applied after the fact.
systemd 259 and the End of cgroup v1
cgroup v1 — the original Linux control group implementation — is no longer supported. systemd 259, which ships with Ubuntu 26.04, works exclusively with cgroup v2, the unified hierarchy that has been the preferred approach since Linux 4.5. The two APIs are not compatible in several critical areas.
What this means practically: Docker has supported cgroup v2 since version 20.10, and standard container configurations work without modification. But older Docker Compose files, Kubernetes configurations, or monitoring agents that reference v1-specific controllers (like memory.memsw.limit_in_bytes or cpuset paths structured under the v1 hierarchy) will fail. Audit your container stack before migrating any production node to 26.04.
Dracut Takes Over from initramfs-tools
The component responsible for building the initial ramdisk — the minimal environment that handles the earliest phase of boot before the main filesystem is mounted — has changed. initramfs-tools, which Ubuntu has used for many years, is replaced by Dracut. Dracut integrates more tightly with systemd during early boot and adds capabilities that initramfs-tools couldn't provide, including Bluetooth support during initialization and NVMe-oF (NVM Express over Fabrics) for booting from network-attached NVMe targets.
For most systems, the transition is automatic and transparent. The risk surfaces if you have custom hooks written for initramfs-tools — scripts that unlock encrypted volumes, mount network shares, or initialize special hardware before the root filesystem appears. Those hooks need to be ported to Dracut's module system before upgrading.
NVIDIA CUDA and AMD ROCm in the Official Archive
Previously, getting CUDA onto an Ubuntu system meant configuring NVIDIA's external package repository, managing keyring files, and trusting a third-party source for packages that sit deep in the GPU computing stack. Ubuntu 26.04 changes the arrangement: CUDA packages are now part of the official Ubuntu archive, maintained and tested by Canonical's team alongside everything else in the distribution.
AMD ROCm follows the same path. Both toolkits are now installable through standard apt commands against Ubuntu's own repository infrastructure. For ML engineers, data scientists, and anyone running GPU-accelerated compute workloads, this simplifies environment setup significantly — and it removes the version management friction that comes with juggling OS packages against vendor-supplied CUDA libraries.
The default proprietary NVIDIA driver has also moved to the 595.x series, and Wayland performance with NVIDIA hardware has improved substantially as a result.
apt Gets a History System
One of the more practical everyday improvements: the apt package manager now tracks a transaction history and exposes commands to work with it.
# See what a past transaction did
sudo apt history-info 0
# Undo the most recent installation
sudo apt history-undo 0
# Redo something that was undone
sudo apt history-redo 0
# Roll back to a previous state
sudo apt history-rollback 1
This closes a usability gap that has existed since Ubuntu's early days. Recovering from an accidental removal or figuring out exactly what an apt upgrade session changed previously required parsing /var/log/dpkg.log by hand. Now it's a first-class feature with predictable behavior.
Developer Toolchain
Ubuntu 26.04 ships a fully refreshed compilation and runtime environment: OpenJDK 25 (certified against the TCK on AMD64, ARM64, S390X, and PPC64EL), LLVM 21 as the default LLVM toolchain, Rust 1.93.1, Zig 0.15.2 with riscv64 support, .NET 10, and glibc 2.43 incorporating ISO C23 additions. This is a meaningful upgrade for anyone developing in compiled languages — especially Rust, where the toolchain version directly affects which language features are available.
On the database side, DocumentDB 0.108-0 is now in the Ubuntu archive. It provides a MongoDB-compatible query interface built on top of PostgreSQL — relevant for teams that need that compatibility layer without commercial licensing considerations. MariaDB 11.8.6 LTS is updated and now ships with an AppArmor profile and a hardened systemd unit built into the Ubuntu package itself. MySQL 8.4 LTS is also available, though MySQL and MariaDB can't coexist on the same host under current packaging constraints.
x86-64-v3 Package Variants
Modern desktop and server CPUs implement instruction sets that weren't available when the x86-64 baseline was defined. Ubuntu 26.04 makes x86-64-v3 package builds available as optional alternatives — these compile against a newer instruction set baseline that includes AVX2 and several other additions present in Intel Haswell-class CPUs and later AMD equivalents.
Nothing changes automatically. Users on older hardware get the same standard packages as before. Those who want to opt in can install the v3 variants and get measurable throughput improvements on compute-heavy workloads. It's a clean approach: optional, clearly labeled, and backward-compatible with the default stack.
WSL Gains Enterprise Management Features
The Windows Subsystem for Linux integration picks up cloud-init support and Ubuntu Pro for WSL in this release. Together, these enable large-scale WSL deployment management through Canonical's Landscape platform — organizations can push configuration, enforce compliance policies, and track security status across WSL instances the same way they manage headless Ubuntu servers. For enterprises that operate mixed Windows/Linux environments, the gap between Windows desktop and Linux tooling infrastructure gets noticeably smaller.
Ubuntu 24.04 LTS vs 26.04 LTS: Side-by-Side
If you're running 24.04 Noble Numbat in production, here's a structured view of what changes across the two LTS generations:
| Area | Ubuntu 24.04 LTS | Ubuntu 26.04 LTS |
|---|---|---|
| Kernel version | 6.8 | 7.0 |
| Desktop environment | GNOME 46 | GNOME 50 |
| Display server | Wayland default, Xorg available | Wayland only; XWayland for X11 apps |
| Terminal emulator | GNOME Terminal | Ptyxis (GTK4, GPU rendering) |
| Default video player | Totem | Showtime |
| System monitor | GNOME System Monitor | Resources |
| Image editor | GIMP 2.10 | GIMP 3.2 |
| initramfs generator | initramfs-tools | Dracut |
| cgroup hierarchy | v1 + v2 | v2 exclusively |
| Disk encryption | LUKS with boot passphrase | LUKS + TPM-backed keystore option |
| CUDA in official repos | No | Yes |
| Default Java | OpenJDK 21 | OpenJDK 25 |
| Rust toolchain | 1.75 | 1.93.1 |
| apt history commands | Not available | history-info, undo, redo, rollback |
| Security support until | April 2029 | April 2031 (2036 with Ubuntu Pro) |
What Works Well
The security improvements in 26.04 are the most durable. Rust rewrites eliminate entire vulnerability classes structurally. TPM-backed FDE removes the operational friction of encrypted-but-unattended servers. CUDA in the official archive means the GPU software stack gets Canonical's security patching cadence rather than depending on NVIDIA's own repository timeline. These aren't incremental hardening tweaks — they change the fundamental properties of the system.
Performance gains are real but hardware-dependent. On recent Intel and AMD CPUs, kernel 7.0's storage improvements and the available x86-64-v3 package variants produce measurable throughput differences in I/O-bound and compute-bound workloads. On older hardware, the experience is comparable to 24.04 with slightly improved desktop responsiveness from GPU-accelerated rendering in GNOME 50 and Ptyxis.
For development work, the updated toolchain is simply more practical. Having Rust 1.93.1, OpenJDK 25, LLVM 21, and .NET 10 available from the distribution's own repositories — rather than requiring PPAs or manual installations — removes friction from the standard developer workflow. On a five-year LTS, that matters from day one.
Where the Risks Are
The Wayland-only shift is the most visible compatibility break. Applications that interact with the X display server at a protocol level — rather than just using X11 libraries — may not work correctly or at all through XWayland. Screen capture software, some VNC and RDP implementations, and a subset of GPU-accelerated applications with X11-specific rendering paths fall into this category. This is largely irrelevant for headless servers but needs attention in desktop and workstation deployments.
NVIDIA hardware has a documented suspend/resume issue on some configurations: resuming from sleep under the Wayland session can produce visual corruption or freezes. This is being tracked and will likely be resolved in a point release, but it's worth testing your specific hardware before rolling out desktop deployments at scale.
The cgroup v2 requirement is the server-side migration risk. It's not a difficult technical problem — the move to v2 has been underway across the container ecosystem for years — but anything in your stack that was explicitly configured for v1 paths will break silently or noisily depending on how the tools handle it. A test deployment against a 26.04 node before committing to a migration plan is not optional.
On the database side: MySQL and MariaDB can't coexist. In practice this is an unusual configuration, but teams running both on a single development box will need to pick one or reach for containers.
Practical Use Cases
1. Web and Application Servers on Cloud Infrastructure
Ubuntu LTS has been the dominant OS choice for cloud server provisioning for years, and 26.04 reinforces that position. The combination of a five-year security commitment, a modern kernel, and production-hardened database packages (MariaDB 11.8.6 with AppArmor, MySQL 8.4) covers the vast majority of web hosting, API serving, and application backend use cases. Teams running LAMP or LEMP stacks on a Serverspace VPS can deploy 26.04 images and get a well-maintained foundation that holds up for years without major OS intervention.
2. GPU Computing and AI/ML Pipelines
The native CUDA availability is specifically aimed here. Research teams, ML engineers, and organizations running inference infrastructure no longer need to manage NVIDIA's repository infrastructure separately. A single apt install against the Ubuntu archive pulls in CUDA with the same dependency tracking and security patching as any other system package. AMD ROCm follows the same pattern. Ubuntu 26.04 LTS is a practical baseline for PyTorch, TensorFlow, and JAX environments that need stability over a multi-year research or production horizon.
3. Developer Workstations and Build Systems
Keeping language runtimes current is one of the persistent annoyances of long-running LTS deployments. Ubuntu 26.04 addresses this at the OS level with a toolchain that reflects 2026's ecosystem rather than requiring workarounds. OpenJDK 25, Rust 1.93.1, LLVM 21, and .NET 10 are all first-class packages. CI/CD pipelines that use Ubuntu LTS as a build base benefit from consistent behavior across a five-year window — fewer surprise breakages from PPA updates or external repository changes.
4. Container Infrastructure and Kubernetes Nodes
Ubuntu is a common choice for Kubernetes worker nodes, and 26.04 maintains that fit — after the cgroup v2 migration is confirmed. Once the container stack is verified, kernel 7.0's storage improvements and the tighter systemd-based boot via Dracut make for a well-integrated node OS. Livepatch support on Arm64 servers also makes this more attractive for aarch64-based cluster infrastructure.
5. Compliant and Security-Conscious Enterprise Environments
TPM-backed disk encryption, Rust utilities, AppArmor profiles for database services, mandatory cgroup v2 (which enables better resource isolation), and ten-year Ubuntu Pro coverage address a cluster of requirements that come up in regulated industries and government deployments. The ability to reach baseline hardening from a standard installation, rather than applying layers of post-install configuration, reduces both setup time and the risk of configuration gaps.
Mistakes Worth Avoiding During Migration
Moving production 24.04 servers before the first point release. Canonical holds the direct upgrade path from 24.04 until Ubuntu 26.04.1 ships in July 2026. This is intentional: the first few weeks of an LTS release are when early-adopter bug reports surface and get addressed. Waiting costs nothing and avoids troubleshooting on live infrastructure.
Skipping cgroup v2 validation before upgrading nodes. The failure mode here is containers that crash, resource limits that don't apply, or monitoring agents that lose visibility — potentially all at once on a production host. Bring up a 26.04 test node, run your container workloads against it, and confirm everything behaves before scheduling the migration.
Treating XWayland as a full X11 replacement. It covers the common cases. It doesn't cover everything. Applications that programmatically control window positioning, capture raw pixel data from other windows, or rely on specific X extensions may fail or behave unexpectedly. If you have specialized desktop tooling in your environment, test it against a 26.04 instance before the rollout.
Enabling TPM-backed FDE without a hardware compatibility check. Turning on full disk encryption with TPM keystore on a machine where Absolute firmware is active, or on an NVMe RAID configuration that hasn't been validated, can prevent the system from booting at all. Always test this on non-production hardware with a recovery plan in place.
Ignoring custom initramfs hooks. If your deployment uses scripts that run during the initramfs phase — for network-based volume unlocking, special storage initialization, or hardware setup — those scripts are written for initramfs-tools. Dracut uses a different module structure. They won't automatically work after an upgrade; they need to be reviewed and ported.
Assuming the MariaDB upgrade is automatic. The jump to version 11.8.6 LTS involves a data format change. Running the package upgrade without performing the recommended schema migration step can leave the database in an inconsistent state. Follow the MariaDB upgrade documentation before touching packages on a production database host.
When to Upgrade
If you're setting up something new — a fresh VPS, a new developer machine, a clean CI runner — install Ubuntu 26.04 LTS now. There's no reason to start on 24.04 when the newer LTS is already available and properly released.
If you're running Ubuntu 25.10, the upgrade path is straightforward. You're already on Wayland-only and Ptyxis. The delta between 25.10 and 26.04 is manageable, and the upgrade prompt through standard system tooling will appear in the coming weeks.
If you're on Ubuntu 24.04 LTS with production workloads, hold until July 2026. The 26.04.1 point release is when Canonical enables the direct upgrade path — and when the early-release issues are most likely to be resolved. There's no security urgency in moving early; 24.04 gets patches through April 2029. Plan the migration, run it in staging, and upgrade when it's de-risked.
Conclusion
Ubuntu 26.04 LTS makes some genuinely decisive choices. Xorg is out. cgroup v1 is out. Rust replaces C in the system utility layer. CUDA enters the official archive. These aren't experimental directions — they're commitments to where Linux infrastructure is actually heading. The release is more secure, more capable for GPU workloads, and more consistent in its assumptions than the previous LTS generation.
The migration caveats are real but bounded. Know your cgroup configuration. Audit your X11-dependent tools. Check your initramfs scripts. Test before you move production. With those steps done, Ubuntu 26.04 LTS — whether on a physical machine, a workstation, or a cloud VPS — gives you a solid five-year runway on a platform that has already done the hard architectural work.
FAQ
The upgrade path opens officially in July 2026, when Ubuntu 26.04.1 LTS is released. Before that date, performing the upgrade manually is technically possible but carries extra risk. For production systems, wait for the point release.
No. Ubuntu 22.04 users need to move to either 24.04 LTS or 25.10 first, then upgrade to 26.04. Jumping across two LTS generations directly is not a supported path.
In most cases, yes. XWayland handles the compatibility layer for X11 applications, and the majority of programs that use X11 libraries will run without any changes. The applications that may have problems are those that talk to the X server at a protocol level — specific screen capture tools, some remote desktop implementations, and programs with X11-specific rendering optimizations.
Standard Docker setups work fine — the engine has supported cgroup v2 since version 20.10. The problem area is configurations that explicitly reference v1 controller paths in resource limits, memory settings, or cpuset rules. Review your Compose files and any custom resource constraints before upgrading container hosts.
Standard maintenance covers five years — security updates through April 2031. Ubuntu Pro extends that with Expanded Security Maintenance for another five years, reaching 2036. A separate Legacy add-on can push coverage out to fifteen years total for organizations that need it.
It needs to be installed deliberately — nothing happens automatically. The difference from previous releases is where the packages come from: instead of configuring NVIDIA's external repository, you pull CUDA through Ubuntu's own archive with a standard apt install command. Same toolchain, different and simpler supply chain.
Both opted out of LTS status for 26.04 due to limited contributor capacity. Ubuntu MATE's project lead stepped away from the project in early 2026; Ubuntu Unity faces similar staffing constraints. They may still produce 26.04 builds without the extended support designation. Other official flavors — Xubuntu, Lubuntu, Kubuntu, Ubuntu Budgie, Ubuntu Cinnamon, Ubuntu Studio, Edubuntu, and Ubuntu Kylin — are proceeding with full LTS status.
