Ubuntu 26.04 LTS (Resolute Raccoon) shipped on April 23, 2026, and its first point release followed on August 27. Half a year in, several version numbers in the launch coverage are wrong, and some never matched the archive. LibreOffice is on 26.2, not 25.8. Go defaults to 1.26. APT reports 3.2. The list below is what the archive actually serves today, not what the beta promised.
This is the full rundown of Ubuntu 26.04 features: kernel 7.0, GNOME 50 on a Wayland-only session, sudo-rs and Rust coreutils as defaults, chrony with NTS, Dracut, the amd64v3 package variant, and the server and toolchain versions. We also ran a real upgrade from 24.04 and recorded what it changes and what it leaves alone, which is not the same as a fresh install. If you only need the side-by-side, the 26.04 vs 24.04 comparison covers that. Every version, error and timing here was captured on Ubuntu 26.04.1 with kernel 7.0.0-38 in October 2026.
Ubuntu 26.04 features at a glance: release date, codename, support
Ubuntu 26.04 LTS was released on April 23, 2026 under the codename Resolute Raccoon (resolute in apt sources). Standard support runs five years, to April 2031. Ubuntu Pro extends security maintenance to ten years. The current build is 26.04.1, and that point release also opened the LTS upgrade path from 24.04.
| Item | Ubuntu 26.04 LTS |
|---|---|
| Codename | Resolute Raccoon (resolute) |
| Release date | April 23, 2026 |
| First point release | 26.04.1, August 27, 2026 |
| Kernel | Linux 7.0 (GA and HWE) |
| Desktop | GNOME 50, Wayland session only |
| Standard support | Until April 2031 |
| With Ubuntu Pro (ESM) | Ten years |
Upgrade from 24.04 via do-release-upgrade | Offered since 26.04.1 |
The official requirements: 6 GB of RAM, a 2 GHz dual-core CPU and 25 GB of disk for the desktop. Server starts at 1.5 GB of RAM and 4 GB of storage. For a lower floor, Canonical points you at Xubuntu or Lubuntu, which run in 2 GB. Our desktop VM (ubuntu-desktop-minimal on a server cloud image, not an ISO install) settled at 1.1 GiB used after login with nothing open, so the 6 GB figure is about headroom for a browser and LibreOffice, not about GNOME itself.
GNOME 50 on a Wayland-only desktop
The desktop jumps from GNOME 46 to GNOME 50, so a 24.04 user gets four GNOME releases at once. The Ubuntu session now runs on Wayland only, because GNOME Shell can no longer start as an X.org session. X11 applications still run through XWayland. KDE, Xfce, MATE and i3 can still be started on X.org. The Settings panel confirms it on a fully updated system:
The changes you notice first are the default apps. Ptyxis replaces GNOME Terminal, Papers replaces Evince, Loupe replaces Eye of GNOME, and Resources replaces both System Monitor and Power Statistics. Showtime replaces Totem as the video player. The Software & Updates app is gone from the default install, though software-properties-gtk is still in the archive. Fractional scaling is on by default, VA-API hardware video decode and encode work by default on AMD and Intel, and JPEG XL opens without extra packages.
We checked which of these actually land with ubuntu-desktop-minimal on 26.04.1:
| Role | Ubuntu 24.04 app | Ubuntu 26.04 app | Installed by desktop-minimal on 26.04.1 |
|---|---|---|---|
| Terminal | GNOME Terminal | Ptyxis | Yes (GNOME Terminal still present too on our cloud-image build) |
| Document viewer | Evince | Papers | Yes |
| Image viewer | Eye of GNOME | Loupe | Yes |
| System monitor | System Monitor | Resources | Yes |
| Profiler | none | Sysprof | Yes |
| Video player | Totem | Showtime | No, desktop-minimal does not pull it in |
Resources is the more useful of the swaps. It groups processes by app and tracks GPU, video engine and NPU load, which System Monitor never did:
Bundled application versions moved on after release. LibreOffice went out as 26.2.2 in the release pocket and is 26.2.6 in updates today. GIMP is 3.2.2. Firefox and Thunderbird are snaps, so they track Mozilla: the release notes list Firefox 150 and Thunderbird 140 at launch, and our desktop pulled Firefox 157 in October.
The rest of the desktop list from the release notes: an official generic ARM64 desktop ISO (VMs, ACPI and EFI machines, Snapdragon-based Windows on Arm laptops), BitLocker-aware dual boot in the installer, the NTSYNC driver for Wine and Proton games, update notifications that no longer steal focus, and Ubuntu Insights as an opt-in replacement for Ubuntu Report. GNOME’s PreLogin and PostSession scripts were removed with the X11 code, which matters in corporate setups that synced home directories at login. The workaround is pam_exec.
Ubuntu 26.04 kernel version: Linux 7.0
Both the GA and HWE stacks run Linux 7.0. The release pocket carries 7.0.0-14. A fully updated system runs a later 7.0 build:
uname -rOur 26.04.1 server reported:
7.0.0-38-genericThe same kernel is now available on 24.04 through its HWE stack: linux-generic-hwe-24.04 resolves to 7.0.0-38 on a fully patched 24.04.5. So a kernel 7.0 requirement on its own is no longer a reason to move off 24.04.
What the 26.04 kernel brings, per the release notes: Panther Lake (Core Ultra Series 3) support with Xe3 graphics and NPU work, the IgH EtherCAT module, ZFS 2.4.1, Kernel Livepatch on ARM64, and DOCA-OFED modules. Upstream Linux 7.0 also dropped the experimental label from Rust support. The real-time kernel now sits in the main archive, outside Ubuntu Pro. sched_ext, which lets you write schedulers as eBPF programs, arrived back in 24.10 and is included.
Two details differ from what most launch posts said. First, linux-lowlatency still exists, but it is now a metapackage that depends on linux-image-generic plus lowlatency-kernel, which tunes the GRUB command line. There is no separate lowlatency kernel build. Second, the installer enables crash dumps by default, but only on qualifying hardware: at least 4 CPU threads, at least 6 GB and under 2 TB of RAM, free space in /var above five times RAM plus swap, and amd64 or s390x (arm64 only with UEFI). Our 4 GB cloud-image VM had no crashkernel= on its command line, so check before you assume kdump is armed.
One kernel regression is in the official known issues. A Linux 7.0 change can cut PostgreSQL throughput and raise latency on systems without huge pages. Set huge_pages = on and size vm.nr_hugepages before you put PostgreSQL on 26.04.
sudo-rs replaces sudo
The sudo command on 26.04 is sudo-rs, a Rust rewrite. The original sudo is still installed as sudo.ws, and the sudo-ldap package is gone (use LDAP through PAM). Password feedback is on by default, so you see an asterisk per keystroke at the new prompt:
To turn the asterisks off, add Defaults !pwfeedback with sudo visudo. sudo-rs accepted that line without complaint in our test.
Most sudoers files work unchanged. The breakage is in flags and settings sudo-rs does not implement. sudo -E is the one scripts hit most:
sudo -E trueIt still exits 0, but the environment is not preserved:
sudo: preserving the entire environment is not supported, '-E' is ignoredA script that relied on -E to pass proxy variables or KUBECONFIG now silently runs without them. Use --preserve-env=VAR1,VAR2, which sudo-rs supports. -b, -A, -g, -i, -s, -l and -n were all accepted in our tests.
Error: “syntax error: unknown setting: ‘requiretty'”
sudo-rs rejects Defaults options it does not implement. We dropped a file with requiretty, timestamp_type=global, lecture=always and insults into /etc/sudoers.d/. The first two failed validation. The other two were accepted silently.
This catches people out: visudo -c reports the file as invalid, but sudo itself keeps working and only prints the warnings on every call. Config management that gates on visudo -c will fail its run. Remove the unsupported lines, or switch the system back to the original sudo:
sudo update-alternatives --set sudo /usr/bin/sudo.wsThe alternative switches immediately:
update-alternatives: using /usr/bin/sudo.ws to provide /usr/bin/sudo (sudo) in manual modeAfter the switch, sudo --version prints Sudo version 1.9.17p2. Run sudo update-alternatives --auto sudo to go back to sudo-rs.
Rust coreutils, and where GNU is still used
Most core utilities now come from uutils, the Rust rewrite. Not all of them do. On 26.04.1, cp, mv, rm and df still point at GNU binaries:
for c in ls cp mv rm cat sort date base64 du df; do printf "%-7s " $c; $c --version 2>&1 | head -1; doneOutput from the test server:
ls ls (uutils coreutils) 0.10.0
cp cp (GNU coreutils) 9.7
mv mv (GNU coreutils) 9.7
rm rm (GNU coreutils) 9.7
cat cat (uutils coreutils) 0.10.0
sort sort (uutils coreutils) 0.10.0
date date (uutils coreutils) 0.10.0
base64 base64 (uutils coreutils) 0.10.0
du du (uutils coreutils) 0.10.0
df df (GNU coreutils) 9.7The uutils package went out as 0.8.0 at release and is 0.10.0 in updates, so behaviour shifts within the LTS. Every GNU tool stays reachable with a gnu prefix (gnuls, gnubase64, gnusha256sum). To swap the whole set back, Canonical documents sudo apt install coreutils-from-gnu --allow-remove-essential. Our Rust coreutils guide goes through the compatibility gaps.
The release notes say the switch brings significant speedups, with base64 as the example. We timed it on a 1 GiB random file, three runs each, on an i7-6700 VM with the host CPU passed through:
| Command (1 GiB file) | uutils | GNU | Result |
|---|---|---|---|
base64, host CPU | 1.23 to 1.29 s | 1.86 to 1.91 s | uutils takes about a third less time |
base64, host CPU, amd64v3 packages | 0.98 to 1.03 s | 1.49 to 1.61 s | uutils takes about a third less time |
base64, kvm64 vCPU | 2.28 to 2.34 s | 1.44 to 1.57 s | GNU takes about a third less time |
sha256sum, host CPU | 7.19 to 7.53 s | 2.92 to 2.99 s | GNU about 2.5x faster |
wc -l, host CPU | 0.16 to 0.17 s | 0.14 to 0.16 s | Even |
The base64 claim holds only when the VM sees the AVX2 instructions of the host. On the generic kvm64 CPU model that many hypervisors still default to, uutils base64 is slower than GNU. And sha256sum was clearly slower in uutils even with the host CPU passed through. If a backup or CI job hashes large files, call gnusha256sum explicitly.
amd64v3 packages and the Illegal instruction trap
Ubuntu now builds an amd64v3 variant of the archive, compiled for the x86-64-v3 level (AVX2, BMI2, FMA, MOVBE). It is opt-in on installed systems. AMD64 cloud images on all providers are built amd64v3 by default, so older platforms cannot run 26.04 images at all. On AWS that rules out M1 to M4, C1, C3, C4, R3, R4, I2, G3, P2, P3 and P3dn. On Google Cloud it rules out N1 machines on Sandy Bridge and Ivy Bridge.
Check the CPU first. The glibc loader reports which levels the CPU supports:
/lib64/ld-linux-x86-64.so.2 --help | grep -A6 "Subdirectories of glibc-hwcaps"You want supported next to x86-64-v3, as on our host-CPU VM:
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)Only then enable the variant:
echo 'APT::Architecture-Variants "amd64v3";' | sudo tee /etc/apt/apt.conf.d/99enable-amd64v3
sudo apt-get update
sudo apt-get upgradeOn our server, the upgrade reinstalled 483 packages as their _amd64v3.deb builds. Version numbers stay the same, so apt list --installed looks unchanged. The .deb names in /var/cache/apt/archives show which builds you got. The gain we measured was modest: base64 went from about 1.25 s to 1.0 s.
Error: “subprocess was killed by signal (Illegal instruction), core dumped”
APT does not check the CPU before it switches to the variant. We enabled amd64v3 on a Proxmox VM with no CPU type set, which falls back to kvm64 and has no AVX2. The x86-64-v2-AES model that newer Proxmox web UI VMs get lacks AVX2 too. apt-get update fetched the amd64v3 indexes without warning, and the upgrade died on libc6:
The box was left with libc6 in the iHR state (half installed, reinstall required). We rolled the VM back from a ZFS snapshot. The fix is on the hypervisor side: give the guest the real CPU flags (on Proxmox, qm set 105 --cpu host for VM 105 or the x86-64-v3 model), cold boot it, and confirm with the loader check above before you touch the APT config. On bare metal, trust the loader check, not the CPU generation. Plenty of post-Haswell parts have no AVX2, including the Gemini Lake J4125 and Jasper Lake N5105 chips in many homelab mini PCs.
systemd 259, tmpfs /tmp and other core changes
systemd moves from 255 to 259. Three changes reach ordinary servers:
- cgroup v1 is gone. A 24.04 host booted with cgroup v1 is blocked from upgrading, and 26.04 cannot run containers that need v1. The cgroup v2 migration guide covers the move.
- /tmp is tmpfs. It is capped at half of RAM, which was 2.0 GB on our 4 GB server. Anything that stages large files in /tmp (database dumps, ISO builds) needs another path such as
/var/tmp. - System V scripts are deprecated. 26.04 is the last release with SysV service script compatibility. Port old
/etc/init.dscripts to units now.
Dracut replaces initramfs-tools as the initramfs generator on new installs and uses systemd inside the initramfs. The Dracut guide for 26.04 covers rebuilding and switching back. Netplan moves to 1.2. Removable media now mount under /run/media/$USER instead of /media; on our desktop the cloud-init seed disc auto-mounted at /run/media/josphat/cidata. Scripts that hardcode /media/$USER need updating.
APT is 3.2 on 26.04.1 (the release notes say 3.1). It uses OpenSSL instead of GnuTLS, pages long output, adds a fallback dependency solver, and can undo transactions. apt-key is gone:
apt-key listOld repository instructions that start with apt-key add now fail at the first line:
bash: line 1: apt-key: command not foundPut the key in /etc/apt/keyrings/ and reference it with Signed-By: in a deb822 .sources file. The new history commands work like this:
apt history-listEach transaction gets an ID you can pass to apt history-info, history-undo or history-rollback:
ID Command line Date and Time Action Changes
0 apt-get install -qqy ... 2026-05-20 16:28:38 Install 6
1 apt-get -q -y -o Dpkg... 2026-06-09 00:32:11 I,U 16
2 /usr/bin/apt-get --op... 2026-10-05 19:56:19 I,U 200Chrony with NTS replaces systemd-timesyncd
New installs use chrony 4.8 instead of systemd-timesyncd, and the default sources use NTS (authenticated NTP) against Canonical’s servers. Check with:
sudo chronyc -N authdataEvery source shows Mode NTS. Without sudo the command returns 501 Not authorised.
Name/IP address Mode KeyID Type KLen Last Atmp NAK Cook CLen
=========================================================================
1.ntp.ubuntu.com NTS 1 30 128 25m 0 0 8 64
2.ntp.ubuntu.com NTS 1 30 128 25m 0 0 8 64
3.ntp.ubuntu.com NTS 1 30 128 25m 0 0 8 64
4.ntp.ubuntu.com NTS 1 30 128 25m 0 0 8 64
ntp-bootstrap.ubuntu.com NTS 1 30 128 39m 0 0 8 64The pools live in /etc/chrony/sources.d/ubuntu-ntp-pools.sources. If you add your own servers to chrony.conf, check you are not listing these twice. Networks that block TCP 4460 (NTS-KE) will see chrony fail to sync. Allow it outbound or point chrony at internal NTP sources.
Security changes: OpenSSH 10.2, TPM encryption, AppArmor
OpenSSH goes from 9.6p1 to 10.2p1. Post-quantum key exchange is the default. On a 26.04 host connecting to itself, ssh -v negotiated:
debug1: kex: algorithm: mlkem768x25519-sha256DSA is removed, DSA host keys are no longer generated, sshd.service is now an alias of ssh.service, and PerSourcePenalties is on by default (sshd -T shows authfail:5 noauth:1 max:600 among others). That last one throttles source addresses that keep failing authentication, so monitoring probes that open bare TCP connections to port 22 can earn penalties. sshd also no longer reads ~/.pam_environment.
On the desktop, the installer offers TPM-backed full disk encryption with an optional PIN or passphrase. The known limits from the release notes: no re-encryption, no DKMS drivers other than NVIDIA, and hardware that needs modules outside the kernel snap (the vmd module for NVMe RAID, for example) is not available. Snap permission prompting is controlled from the Security Center. The AppArmor package ships many new application profiles; if one blocks a legitimate use, the AppArmor guide shows how to read the denial and add a local override. OpenSSL is 3.5 and supports ML-KEM, ML-DSA and SLH-DSA.
Server stack versions: 24.04 vs 26.04
These are the candidate versions apt-cache policy returned on fully updated 24.04.5 and 26.04.1 systems on October 5, 2026, not the launch-day numbers. Most 26.04 packages have moved one or more point releases since April.
| Package | Ubuntu 24.04.5 | Ubuntu 26.04.1 | Watch out for |
|---|---|---|---|
| PostgreSQL | 16 | 18.6 | Kernel 7.0 regression without huge pages |
| MySQL | 8.0.46 | 8.4.11 | mysql_native_password accounts locked out by default |
| MariaDB | 10.11.14 | 11.8.6 | Now in main; conflicts with MySQL |
| Valkey | 7.2.13 | 9.0.4 | |
| nginx | 1.24.0 | 1.28.3 | |
| Apache | 2.4.58 | 2.4.66 | TLS 1.0/1.1 off; MemoryDenyWriteExecute breaks mod_php JIT |
| PHP | 8.3 | 8.5.4 | |
| HAProxy | 2.8.16 | 3.2.9 | tune.ssl.ocsp-update renamed |
| Postfix | 3.8.6 | 3.10.6 | No chroot by default |
| Dovecot | 2.3.21 | 2.4.2 | New config format, migrate by hand |
| Samba | 4.19.5 | 4.23.6 | Install samba-ad-dc before upgrading a DC |
| SSSD | 2.9.4 | 2.12.0 | Runs as user sssd, files provider removed |
| Squid | 6.14 | 7.2 | Several directives removed |
| docker.io | 29.1.3 | 29.1.3 | containerd image store on fresh installs |
| containerd | 2.2.1 | 2.2.2 | |
| runc | 1.3.4 | 1.4.0 | |
| Podman | 4.9.3 | 5.7.0 | |
| QEMU | 8.2.2 | 10.2.1 | New HWE virtualization stack available |
| libvirt | 10.0.0 | 12.0.0 | |
| Incus | 6.0.0 | 6.0.5 |
One row is worth a second look: docker.io on 24.04 has been updated to the same 29.1.3 that 26.04 ships, along with containerd 2.2.1. Docker 29 is no longer a reason to upgrade. On a fresh 26.04 install, Docker uses the containerd snapshotter:
sudo docker info | grep -iE "storage driver|driver-type|cgroup"The storage driver shows as overlayfs with the containerd driver type:
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Cgroup Driver: systemd
Cgroup Version: 2
cgroupnsDocker daemons upgraded from an older docker.io, or configured with userns-remap, keep the classic store. QEMU and libvirt also get a separate HWE virtualization stack (qemu-hwe, libvirt-hwe) that follows interim releases, switchable with ubuntu_virt_helper. For a hypervisor build, see KVM and QEMU on 26.04. OpenStack 2026.1 (Gazpacho) is the bundled cloud release.
Development toolchain and AI/ML packages
Default toolchain versions, again from the live archive:
| Toolchain | Ubuntu 24.04.5 | Ubuntu 26.04.1 |
|---|---|---|
GCC (default gcc) | 13.2 | 15.2 |
| binutils | 2.42 | 2.46 |
| glibc | 2.39 | 2.43 |
| Python | 3.12 | 3.14 |
| LLVM / Clang | 18 | 21.1 |
| Rust | 1.75 | 1.93.1 (1.91 and 1.92 also packaged) |
Go (golang-go) | 1.22 | 1.26 (1.25 also packaged) |
| OpenJDK default | 21 | 25 (26 in universe) |
| .NET | 10 available | 10 available |
| Zig | not packaged | 0.14.1 (default), 0.15.2 |
One of these differs from the release notes. They say Go 1.25, but golang-go has pointed at 1.26 in the release pocket since launch day. Python 3.14 matches the notes. The 3.13 quoted in some early coverage was never packaged on 26.04, so anything that pins python3.13 will not find it.
For AI and GPU work, the archive now carries vendor stacks that used to need third-party repositories. cuda-toolkit installs NVIDIA CUDA 13.1.1 from Ubuntu itself (the driver side is covered in NVIDIA drivers and CUDA on Ubuntu). AMD ROCm 7.1.0 is in universe as rocm and rocm-dev, CI-tested on MI-100, Strix Halo and RX 9070-class cards. The Intel DPC++ compiler (dpclang-6) and oneDNN for Intel GPUs are there too.
Hardware support and flavors
Intel Arc B570, B580 and the Pro B50 to B70 cards, plus Xe2 and Xe3 integrated graphics, are fully supported, including AV1 and HEVC hardware encode. NVIDIA laptops get Dynamic Boost by default and desktops get suspend and resume fixed for Wayland. Platform floors went up: RISC-V needs the RVA23S64 profile (which, per the release notes, no shipping hardware met as of April), and IBM Z needs z15 or newer. Raspberry Pi gets an A/B boot layout that tests new boot assets before committing them, so update the Pi 4 and Pi 5 EEPROM before you install.
Flavors: Kubuntu, Xubuntu, Lubuntu, Ubuntu Budgie, Ubuntu Cinnamon, Ubuntu Studio, Edubuntu, Ubuntu Kylin and Ubuntu Unity all publish 26.04 release images on cdimage.ubuntu.com. Ubuntu MATE does not (the 26.04 path returns 404). MATE users can stay on 24.04, whose flavor support ends in April 2027, or wait for MATE 26.10, which already has a beta ISO.
Known issues still open
From the current release notes, the ones most likely to affect you: the PostgreSQL slowdown on kernel 7.0 without huge pages; mod_php JIT warnings (Allocation of JIT memory failed, PCRE JIT will be disabled) caused by the new Apache MemoryDenyWriteExecute=yes, fixed by moving to php-fpm or overriding the unit; GTK 4 apps rendering badly in VirtualBox and VMware with 3D acceleration on; and a Ventoy release that breaks booting the installer (flash the ISO directly or use Ventoy 1.1.10). The 30 second first-boot delay on Google Cloud images from launch is fixed in 26.04.1 (systemd 259.5-0ubuntu3.3), so it only bites images built before that update reached the archive in August 2026 (LP #2148619). The official known-issues page still lists it. RabbitMQ also needs manual feature-flag steps before an upgrade.
What a 24.04 upgrade changes and what it leaves alone
The LTS upgrade is open. On a 24.04.5 server, /etc/update-manager/release-upgrades has Prompt=lts and the check offers 26.04.1. The first attempt failed because the box had pending kernel and libc updates:
Checking for a new Ubuntu release
You have not rebooted after updating a package which requires a reboot. Please reboot before upgrading./var/run/reboot-required.pkgs listed libc6, apparmor, linux-base and the new kernel. Reboot, then run the upgrade. Take a snapshot or backup first, because the non-interactive mode answers every prompt for you, config-file questions included. Over SSH, the upgrader also starts a spare sshd on port 1022 in case the main one drops. It does not open that port, so allow 1022 in ufw or your cloud security group first if you want the fallback. Non-interactively it took 10 minutes on a 4 vCPU VM:
sudo DEBIAN_FRONTEND=noninteractive do-release-upgrade -f DistUpgradeViewNonInteractiveAfter one more reboot, the system was on 26.04.1 with kernel 7.0, but it was not the same as a fresh install:
Side by side with the fresh install on the same point release:
| Component | Fresh 26.04.1 install | 24.04.5 upgraded to 26.04.1 |
|---|---|---|
| sudo | sudo-rs | sudo-rs (switched) |
| coreutils | uutils, GNU cp/mv/rm/df | Same (switched) |
| /tmp | tmpfs | tmpfs after the reboot |
| Time sync | chrony with NTS | systemd-timesyncd (kept) |
| initramfs | Dracut | initramfs-tools (kept) |
To bring time sync in line with new installs, follow the release notes: mark timesyncd as automatically installed (ours already was), then install chrony. APT removes systemd-timesyncd in the same transaction, and chrony picks up the NTS pools:
sudo apt-mark auto systemd-timesyncd
sudo apt-get install -y chronyBefore you run the upgrade on a real server: confirm cgroup v2 (stat -fc %T /sys/fs/cgroup must print cgroup2fs), install samba-ad-dc on Samba domain controllers, grep your sudoers for requiretty and timestamp_type, move anything large out of /tmp, and plan the Dovecot 2.4 config migration. The full step-by-step walkthrough is in the 24.04 to 26.04 upgrade guide. For a new server, start with the initial server setup and the post-install checklist, then check the official LTS summary and the 26.04.1 changelog for anything specific to your stack.
Very helpful to me noobie.
Installation done. Now I need how to explore my computer music, documents, and browsers.
thanks..
Your documents and music live in the Files app, the folder icon in the dock, under Home, Documents, Music, and Downloads. Firefox is the preinstalled browser. Press the Super key and type an app name to launch anything else.