Ubuntu 24.10 is available to download and install from the official website. It ships with the Linux 6.11 kernel and the latest GNOME 47 desktop enviroment. This version switches to Wayland by default for hardware with NVIDIA graphics, matching the previous Xorg transition for Intel and AMD graphics users, and uses the open-source NVIDIA 560 kernel modules by default on supported hardware. The kernel also has kdump-tools, which enables kernel crash dumps by default. This helps streamline troubleshooting by automatically capturing critical data after a crash.
Canonical also said in its blog post, “For gamers, significant improvements have also been made to the compatibility of the Steam snap, with an expanded permissions model and improved NVIDIA driver support. The Steam snap also bundles gaming-specific Mesa PPAs to deliver optimized performance out of the box when combined with the low latency settings enabled in the latest kernel.”
Updates are also visible in the Ubuntu Dock, which better handles Progressive Web Applications. The OpenJDK 21 and OpenJDK 17 packages in Ubuntu have also changed and are now TCK (Technology Compatibility Kit) certified on amd64, arm64, s390x, ppc64el, and armhf. Passing the TCK tests means the OpenJDK packages for version 17 and version 21 on Ubuntu are compliant with the Java SE specification for their corresponding versions.
24.10 is the first release I’ve had with major problems
It’s Kubuntu for me, not Ubuntu, but yay shouldn’t matter
Upgrade from 24.04 to 24.10 failed spectacularly, first upgrade failure in like a decade or so?
So I reinstalled, added crypttab and fstab devices, reboot, then that failed. For some reason, crypttab isn’t working right.
In any case, I boot into an emergency she’ll because of that, but systemd (frack systemd, just like snap) complains about /usr/sbin not being a symlink, saying its critical and why it can’t boot
Eh, okay? I merge it with /usr/bin, symlink it, systemd happy. Things still seemed to work, so yay! Well, crypttab still isn’t but we’ll figure it out, let’s get to work first!
Cue a few days later, most has been setup, and I want to install docker. Docker installation failed because a dependency failed to find a file. I can’t even remember the last time that happened. I can’t cancel the install either, so it’s stuck and I can’t install anything else.
After a day I figure out how to cancel the install completely by cancelling literally docker and every dependency, great.
Work a long time trying to investigate what’s wrong, now I find other packages failing as well. Loads of searches later I figure out that apt hates /use/sbin is a symlink. Frack me for listening to systemd
Try to split it again, copying contents of bin to sbin, nope. Try to put backup directories back, nope.
Reinstall, and prep for attempt #3
Install again, all seems okay, but when adding crypttab and fstab devices, won’t boot again.
This release sucks