In their meeting today the Technical Board approved three year LTS
qualification for the following flavours, following the Release Team's
recommendations:
Ubuntu Budgie
Ubuntu Kylin
Xubuntu
Lubuntu
Edubuntu
Ubuntu Studio
Ubuntu Cinnamon
We haven't seen LTS requalification requests from Ubuntu MATE nor Ubuntu
Unity, so these will release subject to release team approval, and they
will be non-LTS.
Thank you to all the flavours for your work, and to the release team for
reviewing!
On behalf of the Technical Board,
Robie
As OMG! Ubuntu’s Joey Sneddon notes, they might have forgotten about Kubuntu (he’s expecting Kubuntu 26.04 to be an LTS release, too), but the two flavors that are clearly excluded are Ubuntu MATE and Ubuntu Unity.
Joey:
Official Ubuntu flavours only provide 3 years of guaranteed support anyway, not the 5 years regular Ubuntu receives (which extends to 10 years with Ubuntu Pro, and up to a further 5 years with ESM from Canonical).
Flavours don’t stop getting updates after those 3 years, though. Nor do their maintainers lose the ability to issue updates.
Similarly, non-LTS flavours in an LTS cycle get the same foundational updates, including hardware enablement (HWE) stacks. They don’t, however, issue point releases that roll those updates, fixes and kernel uplifts in a new ISO at periodic intervals.
But I wonder how much can anything be guaranteed in Ubuntu land. Ubuntu Pro was supposed to extend the guaranteed support for all official flavors from 3 to 10 years, not only the main flavor’s guaranteed support from 5 to 10 years! Of course, as long as the respective flavor is an approved LTS one!
I’m not that sure that so many people at Canonical are really aware that Ubuntu Pro should extend everything to 10 years in an LTS, regardless of the flavor. I couldn’t care less that Liam Proven, despite being an IT veteran, never learns and doesn’t understand how Ubuntu Pro works. But there seems to be some confusion even among the Ubuntu people! (Note: “esm-infra” refers to the security updates provided for packages in main and restricted; “esm-apps” are the security updates provided for universe and multiverse packages. Non-GNOME desktop environments are in universe. Ubuntu Pro extends this support from 5 to 10 years for “esm-infra” and from “best effort by the community” to 10 years for “esm-apps”!)
It was known that Ubuntu Unity, which didn’t even release 25.10, is as good as dead. While I am certainly not a fan of Unity, it should have attracted more developers, as ❶ it was Canonical’s kid and Canonical’s response to GNOME3, and ❷ it’s a closer match to the macOS visual metaphor than GNOME, if we only consider the global menu! But one cannot find common sense in retards.
But the really bad news is that this is the best proof that Ubuntu MATE is undermaintained. It should have been obvious, and I criticized some obvious flaws:
The Disk Mounter Applet is constantly crashing on my flash drives (one in 3-4 times), and not only isn’t anyone fixing this bug, but nobody even reported it!
The way MATE 1.28 has been released made its inclusion in Debian impossible, meaning that Ubuntu was also stuck with 1.26 for almost two years already. (MATE 1.28 entered Debian testing on Oct. 28.)
When Ubuntu MATE’s team can’t be bothered to even want to have the 26.04 release qualify as LTS, how can anyone believe in Ubuntu MATE’s future?
Oh, but there was one more sign that the Ubuntu MATE guys stopped caring about their child.
As I described in A few Ubuntu MATE idiosyncrasies, the “Welcome” screen in the Live session, which in previous versions also included onboarding functions, has changed drastically in 24.04 LTS. And I included screenshots from the “Welcome” tool in Ubuntu MATE 22.04.5: the user had to click on the “Desktop Layout” button to get the last screen, so all seven layouts can be seen.
In Ubuntu MATE 24.04 and newer, there is no onboarding of any kind, no information that the user can change the layout from a predefined set! How would the user know that there is a MATE Tweak tool with nice predefined layouts? Even if the user finds such a tool in the menu, there are no previews of how these layouts look!
The Ubuntu MATE team has just replaced their customized and informative install and post-install tool with the bland installer from Ubuntu’s main flavor, ditching their own good work! Fucking retards.
Did you know how retarded Clem’s Nemo was?
No, you did not.
Cinnamon was supposed to be a better GNOME that isn’t frozen in time like MATE but evolutionary and revolutionary. Mint, too, benefited from a lot of care from Clem and his minions, even if most of the efforts were directed to futile changes in colors or similar failed attempts to beautify both Cinnamon and Mint. But Cinnamon surely is the smartest file manager once we remove Dolphin from the comparison, right?
Cinnamon 6.6 features improved support for keyboard layouts and input methods.
In the past, the keyboard settings and the keyboard applet only handled traditional layouts.
Going forward, traditional layouts and IBus input methods will be presented in the keyboard settings alongside each other, as if they were the same.
In this screenshot you can see a list of two layouts. One is a traditional XKB layout: French accents on a US ANSI layout. The other is actually an IBus input method: Japanese, using the Mozc engine.
Debian Live ISOs first began to include ready-to-use IBus input-method packages for Japanese, meaning ibus-mozc or fcitx-mozc on the Live image, in Debian 12 Live media in mid-2023. (But general support, with packages installable after boot, has existed at least since Debian 10 in mid-2019.)
Linux Mint discovers Japan on the map in December 2025.
New menu
Nope. Skipping. It’s annoying, with 3 levels, each with different icon sizes!
Nemo
Nemo 6.6 features a template manager: … File operations (copying, moving, etc.) can be paused and resumed.
File operations can be paused
Oh my, oh my, oh my! File operations could not be paused and resumed in Nemo prior to version 6.6!
How the fuck was I supposed to know? I’m not a member of Clem’s sect, and I always thought Cinnamon to be a poorly designed desktop environment!
But Thunar already has a Pause/Resume capability in the file copy/move dialog!How come Nemo is so… retarded?!
Nemo was derived from the old Nautilus that’s now Caja (GNOME’s Files is a “castrated” Nautilus). To the point, Nemo is a 2011 fork of Nautilus 3.4, the last “classic” version before GNOME started ripping stuff out (spatial mode, dual panes, tree view, compact list view, etc.). MATE’s Caja branched from the same 3.4 snapshot, so Nemo and Caja are siblings; both kept the feature set that GNOME later dropped. And yet, the only one that until now lacked a Pause/Resume feature was Nemo!
🟢 Caja does have Pause/Resume:
ℹ️ Caja inherited this capability from the GtkFileOperations code present in Nautilus 2.32 (GTK2), which already had Pause/Resume. When the entire MATE was ported to GKT3, this feature was preserved. In contrast, GNOME 3.0 to 3.6 shipped Files with a brand-new, stripped-down progress that only offered Cancel! The Pause/Resume feature was added back only in GNOME 3.8 (March 2013) when the developers wired the existing gio pause logic to a new button!
🔴 Nemo 6.4.5 does not! What’s worse, there is a disabled start/resume button that makes no sense!
🟡 Nemo 6.6 replaced the disabled shit with a pause button:
ℹ️ To avoid porting code from GTK2 to GTK3, Nemo has forked Nautilus from GNOME 3.4 (the first GTK3 cycle), after GNOME had already thrown the old dialog away and replaced it with a minimal shit that only offered Cancel! Users have been asking for the missing button for years, since Issue #1786: Add pause/resume option to copy dialog (Feb. 23, 2018). But Clem’s team only implemented it in 6.6.
🟢 Thunar does have Pause/Resume:
ℹ️ Actually, Thunar got it not that long ago. Pause/Resume was implemented in Thunar 4.15.1, hence in the stable version 4.16 (December 22, 2020), meaning Xubuntu 21.04, Fedora 34, Debian 11. Still, 5 years before Cinnamon’s Nemo!
🤯 How the fuck are people fascinated by Mint and Cinnamon?!
If you need snaps, then you need this
People being sheeple, and snaps most likely becoming unremovable starting with 26.04 (unless Mint makes a miracle), users of any and all Ubuntu flavors and derivatives (such as Linux Lite) will have to live with snaps.
Too bad it has no mechanism to scan all your snaps, nor is there a way to generate and create a list of the snaps you have on your machine. It’s a hand job so far.
He’s wrong. No, package managers aren’t that smart, and I definitely had my time with them. Two documented examples:
When I wrote The Arch way in Manjaro: replacing the kernel under my ass, the story started by showing how pacman is completely stupid in solving package dependencies, and Pamac wasn’t any smarter; but Octopi is much smarter, and it behaved as it should. Therefore, the dependencies were correctly defined within Arch’s architecture, but the solver was retarded in pacman.
In A random discovery about zypper, thanks to rpm and a deb package, I described a flaw in SUSE’s zypper. It had nothing to do with dependencies but with modes, and when zypper forced an installation, it made a directory writable. That’s a security issue, but still, a package manager that failed.
I have the same talent as that guy to find bugs everywhere. However, package managers are mostly OK, at least as far as apt and yum/dnf are concerned.
The guy in question didn’t understand what package management does.
What happened is this (and I just ignored pacman):
It was not a question of package managers not understanding what the correct dependencies were.
It was not a question of package managers installing “recommended” packages as hard dependencies.
It was a question of how the packager has defined the dependencies in a package’s declaration!
To put it simple:
Package A strictly requires package B to work without crashing.
For some features, package A would require package C, but these features aren’t that frequently used, so let’s put package C as “recommended” (soft dependency).
For some other features, package A would require package D, and the packager has decided to declare package D as “dependency” (hard dependency).
So, the “optimal” case would be to only have package B installed in addition to package A. But once package D is pulled in, this one has its own dependencies, which in turn might have their extra dependencies, and it gets to what you could read in the aforementioned article. The unwise decision was with the packager, not with the package manager’s dependency solver!
Even without installing the “recommended” packages, removing Package A will leave “orphans” installed. Overall, though, unless the packager has declared as hard dependencies packages that pull in an excessive amount of large packages, it’s rather normal.
In RPM land, I’ve encountered the opposite scenario, both in Fedora and in EPEL: the packager has forgotten to add some required dependencies, so the rpm installed, but the binary crashed. Go figure. One can’t have the cake and eat it (on ne peut pas avoir le beurre et l’argent du beurre).
Otherwise, there is always room for improvement. Current development for apt is primarily driven by Julian Andres Klode. If you have the brains to understand more about dependency solving, here you have some hard nuts on his blog:
The last one is nice. And no, I don’t know how they do it in dnf or how they were doing it in yum. That is, I couldn’t tell whether apt is smarter than dnf or vice versa.
HAL -December 22nd, 2025 at 8:01 PMnone
Comment author #116350 on Bad news in Ubuntu land, Nemo was retarded, and more by Homo Ludditus
they might have forgotten about Kubuntu (he’s expecting Kubuntu 26.04 to be an LTS release, too)
Hmm, maybe, yes, but it’s not at all certain. It seems a little strange to “forget” a flavor as important as Kubuntu, which is often one of the first, if not the first, that people mention when talking about them.
This blog uses technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent will adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Hmm, maybe, yes, but it’s not at all certain. It seems a little strange to “forget” a flavor as important as Kubuntu, which is often one of the first, if not the first, that people mention when talking about them.