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
How are you trying to install docker? I wouldn’t be surprised if the docker ppa was unsupported for 24.10.
They should of just backed down and listened to community feedback after the first failure. Instead they pissed everyone off.
Seriously, what’s with that tunnel vision on snaps?
Best case scenario: sunk cost fallacy
Worst case scenario: there’s a lot of shit you can do when you control a closed source app store, and canonical has a history of doing sketchy shit like selling user data to Amazon
Probably secret payments from storage manufacturers. Snaps are huge compared to regular installs.
If you tar or rsync backup starting at your root file system without special precautions, you’ll save them multiple times (at least one version of the snap package plus the contents wherever it’s mounted). After restoring from such a backup, it’s even worse, as you’ll unpack the contents in its not yet mounted mount point first, then, during boot, it will mount the container over it.
They are backtracking and allowing deb out of the box again
the ubuntu machines at work are nearly unusable bc snaps don’t play well with our intranet setup and it just so happens that ubuntu thought it would be a brilliant idea to make firefox, the default browser, a snap
slack is also a snap so the support team had to install it by hand so that we don’t get locked out of work meetings while at the office
this sucks so much bc ubuntu is basically the first distro that comes to mind when ppl think “linux”, so it shouldn’t make us deal with this kind of bullshit. i wish they went back to the days where ubuntu was just a boring repackaged debian
this is pretty much my one problem with ubuntu, and it taints the entire experience tbh. its first time in years i dont look forward to updating because ill have to yank out snaps and figure out how to de-migrate my stuff back to flatpak.
Snnnnap.
That’s a no.
Been using ubuntu for almost 15 years. My annoyance with snap made me just switch to bazzite (gaming focused fedora atomic ). Takes a little getting used to since its immutable but im liking it alot more so far.
Lol I tried to install it on a test machine (not a WM) and I couldn’t do it cuz of some snap failure. Though the latest Canonical’s attempts to add a permission control system for snaps are very interesting to me. Ik Flatseal and KDE’s implementation exist but having a really well made and integrated one can be a big deal for many users. If only it was for Flatpak…
Snaps have had a permission system for at least 5 years now.
Small is inherently slow though. That’s just due to the framework, so any extra work they put into securing it better is just going to make it slower. Flatpak works great, on the other hand.
Doesn’t actually seem like a bad release at all.
But I’m pretty married to Flatpaks at this point so no thanks, I’m good.
Flatpak works on Ubuntu…
And Snaps work outside of Ubuntu…
My point is, Ubuntu goes out of their way to make installing stuff as anything other than a Snap a hindrance.
Their new storefront, which was originally a community creation that allowed for the installation of debs and snaps, initially had deb support ripped out of it when Ubuntu started using it. Only after backlash did they reluctantly add it back. You certainly can’t install Flatpaks through it (unless someone has a fork).
Why would I use a system that so aggressively pushes a packaging format I don’t want to use and suppresses ones that I do?
I guess it matters if you use GUI tools to install things. I almost never do so I hadn’t even noticed.
Even using apt to install things has lead to some things actually being installed as Snaps, unfortunately.
Sure - but I guess I just don’t care? I don’t understand the snap hate. They work fine. Better than flatpaks even. I install some things from flatpak (desktop GUI only stuff) and some things from apt/snaps.
The Snap hate makes perfect sense. It performs worse, each app is mounted as it’s own fs which clutters my file manager, they cause all kinds of issues (e.g with Steam), the sandboxing only works on one distro, there’s a proprietary element to them, they’re controlled by one organisation that’s somewhat questionable, and they undermine the actual packaging standard that seemingly everybody else has adopted.
It’s perfectly reasonable not to want them, and it’s very reasonable not to want them forcibly installed without consent when you’re trying to install something else.
If you like them, fair enough. But I’ve explained why I don’t, and you liking them does not invalidate all the people that don’t like them.
I love how people say “forcibly installed” like it’s rape or something… You haven’t been violated, you’ve been, at worst, mildly inconvenienced.
I can understand people not preferring them. But the whole “forced on me” victim stuff is over the top.
i would let this one cook for a bit longer. the upgrade went fine but the OS has been peculiar (GPU and performance issues, resume from stand by), no actual crashes though
