Ubuntu 26.04 LTS (Resolute Raccoon) Released: What's New and What Changed from 24.04
Canonical released Ubuntu 26.04 LTS (Resolute Raccoon) as the latest long-term support release. Shipping with Linux 7.0, APT 3.2's native rollback features, Wayland-only GNOME 50, and significant server component upgrades, this release targets systems wanting the latest technologies with 5–15 years of support.
Support timeline: 5 years standard (until April 2031), 10 years with free Ubuntu Pro, 15 years with paid Legacy add-on.
Desktop highlights
Wayland-first architecture
Ubuntu 26.04 LTS Desktop ships GNOME 50 as Wayland-only by default. X11 applications still work via Xwayland, so existing software continues to run without modification. However, this is a meaningful shift from 24.04's X11-as-default approach.
⚠️ If you use specialized X11-only tools, confirm Xwayland compatibility before upgrading. Most software works fine, but niche applications (some scientific tools, legacy CAD software, certain VPN clients) may have issues.
Hardware-backed encryption with TPM
The Ubuntu Desktop installer now detects Trusted Platform Module (TPM) 2.0 chips and automatically configures hardware-backed LUKS encryption. If you have TPM 2.0 (most modern laptops and servers do), the installer will:
- Detect TPM 2.0 availability
- Use it to unseal the LUKS key on boot
- Automatically decrypt the filesystem without prompting for a passphrase
This reduces boot friction while maintaining security. The encryption key is sealed to the TPM's Platform Configuration Registers (PCRs), so the system only decrypts if the firmware and bootloader haven't been tampered with.
Automated installation via Landscape
Ubuntu 26.04 LTS integrates Landscape for unattended installation on servers. For fleet deployments, you can define configuration profiles and have systems automatically configure themselves without manual intervention.
New/replaced default applications
| Component | 24.04 | 26.04 | Change |
|---|---|---|---|
| Video player | Totem | Showtime | Faster, better codec support |
| System monitor | gnome-system-monitor | Resources | Cleaner UI, better resource usage tracking |
| File indexer | Tracker Miners | LocalSearch | Faster, lighter indexing |
| Desktop installer | Ubiquity | Subiquity | More modular, TPM support |
| Package manager | APT 2.9 | APT 3.2 | Native rollback/undo/redo |
GPU acceleration improvements
- NVIDIA CUDA: Native driver support baked into the installer; CUDA toolkit available in apt
- AMD ROCm: Same treatment; GPU compute workloads have first-class support
- VA-API: Video acceleration for encoding/decoding enabled by default on Intel and AMD iGPUs
Server-side changes
Linux kernel: 6.8 → 7.0
Linux 7.0 brings:
- io_uring improvements: Better async I/O, especially for database and storage workloads
- LSFMM scheduler refinements: Better CPU scheduling under high load
- Bluetooth 6.0: If you deploy Bluetooth-enabled IoT infrastructure
- FUSE improvements: Better stability for FUSE-based filesystems (e.g., rclone mounts)
- Core hardening: Additional mitigations for CPU side-channel exploits
For most server workloads, the jump from 6.8 to 7.0 is stability + performance, not a breaking change.
APT 3.2: Native rollback (major quality-of-life improvement)
This is the standout feature. APT 3.2 introduces transaction undo/redo/rollback, bringing Debian/Ubuntu to feature parity with DNF (Fedora):
# Install a package
apt install some-package
# Oops, it broke something. Undo the last transaction.
apt undo
# Or redo if you changed your mind
apt redo
# Or view transaction history
apt history
# Or rollback to a specific point
apt rollback 5 # Go back 5 transactions
This is game-changing for production servers where a package update silently breaks something. No more "I installed X and now Y is broken and I can't remember what changed." Just apt undo and you're back to the known-good state.
⚠️ This doesn't replace proper testing in a staging environment, but it's a lifesaver for unexpected breakage.
Database and middleware versions
| Component | 24.04 | 26.04 | Notes |
|---|---|---|---|
| PostgreSQL | 16 | 18 | Improved JSON, performance gains |
| MySQL | 8.0.36 | 8.4 | Group replication improvements |
| MariaDB | 11.4 | 11.8.6 | Faster, more MySQL 8.0 compatible |
| PHP | 8.3.6 | 8.5.2 | JIT improvements, better perf |
| Python | 3.12 | 3.13 | Performance enhancements |
| OpenStack | 2024.2 | 2026.1 | Two releases of improvements |
| containerd | 1.7.x | 2.2.2 | Major version jump, OCI improvements |
| Docker | 27.x | 29 | Better rootless mode |
| QEMU | 9.0 | 10.2.1 | More architectures, better KVM |
| PostgreSQL | 16 | 18 | Better concurrency, performance |
| Samba | 4.21 | 4.23 | SMB 3.1.1 improvements |
| HAProxy | 3.0 | 3.2 | Load balancing improvements |
Other server-side components
- Chrony 4.8: Better time synchronization, NTP improvements
- OpenLDAP 2.6.10: Directory services updates
- SSSD 2.12: System Security Services Daemon improvements
- Squid 7.2: Caching proxy enhancements
- DocumentDB 0.108: MongoDB-compatible document store
- Valkey 9.0: Redis fork with improvements
What changed from Ubuntu 24.04 LTS
Breaking changes and gotchas
- Wayland-only GNOME Desktop
- Desktop installs now use Wayland exclusively
- X11 apps work via Xwayland, but performance may differ
- Some tools (remote desktop, certain VPN clients) may need testing
- Removal of Software & Updates app
- GUI for repository management is gone
- Use command-line tools or Landscape instead
- Repository editing is now CLI-only:
nano /etc/apt/sources.listor/etc/apt/sources.list.d/*.sources
- containerd 1.7.x → 2.2.2 (major version bump)
- If you're running Kubernetes or Docker via containerd, the jump is significant
- Test before upgrading production clusters
- OCI runtime handling changed; custom configurations may need updates
- systemd changes (not unique to 26.04 but worth noting)
- Further hardening of default service restrictions
- Some legacy services may fail to start without explicit override
- Check your critical service units with:
systemd-analyze security <unit>
- APT transactions
- The new rollback feature is opt-in for automated tools
- If you're using apt-listchanges, unattended-upgrades, or other automation, test the interaction first
- Regular
apt installworks as before
Migration path: 24.04 → 26.04
In-place upgrade (recommended for most):
# 1. Update current system
sudo apt update && sudo apt upgrade
# 2. Remove any PPA-held packages or pinned versions
# (Check with: sudo apt-mark showhold)
# 3. Start the dist-upgrade (safe for LTS → LTS)
sudo apt full-upgrade
# 4. Do the actual release upgrade
sudo do-release-upgrade
# 5. Review the prompted changes and confirm the upgrade
# The tool will handle kernel, GNOME, APT, etc.
# 6. Reboot
sudo reboot
Fresh install (if you want a clean slate):
Download from https://releases.ubuntu.com/26.04/ and reinstall. Takes longer but guarantees no cruft from 24.04.
Testing before you upgrade production
For servers in production:
- Clone the server VM or take a snapshot
- Run
sudo do-release-upgrade -don the clone (dry-run mode) - Review what would change
- If it looks safe, run it on the clone for real and test the application
- If something breaks, you still have the original running
- Once confident, schedule the production upgrade
For infrastructure-as-code (Terraform, Ansible):
- Test the upgraded images in a staging environment
- Verify all your automation scripts work with the new versions (PHP 8.5, PostgreSQL 18, etc.)
- Update your automation to target Ubuntu 26.04 noble
- Roll out in stages (dev → staging → production)
Who should upgrade (and who should wait)
Upgrade now (Ubuntu 26.04 is ready for):
- New deployments: If spinning up new servers, use 26.04 immediately
- Development/staging: Fresh environments benefit from latest kernel, databases, APT rollback
- Single-machine workstations: Desktop users wanting GNOME 50 and Wayland
- Small production servers: 1–10 servers with minimal custom dependencies
Wait a month or two (until May/June 2026):
- Large production clusters: Let others find the edge cases first
- Heavy customization: If your servers have lots of custom packages, PPAs, or pinned versions
- Legacy applications: If you rely on older libraries that might not play well with the new versions
- containerd/Kubernetes in production: The 1.7 → 2.2 jump is significant; wait for the ecosystem to stabilize
Keep 24.04 LTS for now:
- Specialized workloads: If you have niche scientific software, legacy CAD, or very specific X11 requirements
- Zero-change stability: If your system is running perfectly and you have no pressing need to upgrade
- Long support windows: 24.04 LTS is supported until April 2029; you have years before end-of-life
24.04 will continue receiving security updates and stability patches through 2029, so staying on it is a valid choice.
Key improvements worth noting
For database workloads
PostgreSQL 18 brings meaningful performance gains for OLTP and OLAP. If you're running heavy database work, the upgrade is worthwhile.
# After upgrade, check what's available
apt-cache policy postgresql
# Or stick with PostgreSQL 16 if you prefer
# (Ubuntu maintains multiple versions in the repository)
For container/orchestration workloads
containerd 2.2.2 and Docker 29 with better rootless mode support. If you're running Kubernetes, verify your distro's tested version before upgrading production clusters.
For desktop users
GNOME 50 is a solid release. Wayland-by-default improves performance on modern GPUs. Test before upgrading if you have specific hardware (external displays, docks, specialized peripherals).
For sysadmins
APT 3.2 rollback is transformative. It turns botched package updates from "restore from backup" into "apt undo" (10 seconds instead of 30 minutes). This alone makes the upgrade worthwhile for systems you manage.
Support and security
Ubuntu 26.04 LTS will receive:
- 5 years standard support (until April 2031)
- 10 years with Ubuntu Pro (free, includes security patches and compliance certifications)
- 15 years with Ubuntu Pro Legacy add-on (paid, for organizations with extreme retention requirements)
Security updates are rolled out as they're available, not batched. Critical kernel or library vulnerabilities are pushed within days.
Summary: upgrade worthiness by role
| Role | Recommendation | Reason |
|---|---|---|
| Sysadmin (servers) | Upgrade staging first, production in 6 weeks | APT rollback, Linux 7.0, test thoroughly |
| DevOps (containers) | Test in k8s lab, upgrade in 2-3 months | containerd 2.2 is significant |
| Desktop user | Upgrade if you like Wayland, wait if you don't | GNOME 50, Wayland-only is the main thing |
| Hosting provider | Wait until June 2026 | Let the ecosystem stabilize |
| Enterprise | Stick with 24.04 unless you have a specific need | More time to test, 24.04 is solid for years |
Bottom line: Ubuntu 26.04 LTS is a quality release with meaningful improvements (APT rollback, Linux 7.0, modern stacks). It's not a must-upgrade, but it's safe to upgrade staging/non-critical production now, and production in 4–6 weeks after others have found any issues.
Download from https://releases.ubuntu.com/26.04/ and see the full release notes at https://documentation.ubuntu.com/release-notes/26.04/.