The Swap, Not the Retrofit: Why Ubuntu Core Desktop Might Fix Snap
Four months ago I ended The Ubuntu Lovers’ Blues with three asks of Canonical. The third was the blunt one: commit to a date for Ubuntu Core Desktop, or concede the desktop layer to Flatpak. “In due course” had already outlasted an entire LTS cycle.
Last week Jon Seager, Canonical’s VP of Engineering for Ubuntu, went on LINUX Unplugged 692 and named one. Ubuntu Core Desktop images released alongside standard Ubuntu with 28.04 LTS. A “stretchy stretch goal” of making it the default in 30.04, which he called “an incredibly aggressive timeline” before anyone else could. A dedicated team, a restart announced in his own post a fortnight earlier, and developer preview images already sitting on GitHub. After a full LTS cycle of “in due course”, that’s a release number with a person’s name attached to it.
I’ve been interested in immutable desktops for a long time, long enough to have a NixOS test repository sitting in my projects folder that I never actually ran. It wasn’t laziness. It just never climbed high enough up a list that also has paying work, a long-range wireless network and this site on it. So it was a small jolt to hear Seager mention that his first three and a half years at Canonical were spent daily-driving NixOS. The person now steering Ubuntu took the detour I kept meaning to take, and came back convinced snaps are the answer. That’s probably worth listening to properly, so I listened twice and checked the transcript.
The Retrofit Problem

I’ve always agreed with the security case for snaps. The earlier post spent its opening section on it: dpkg was designed in 1993 on a total-trust model, every package and every PPA gets root, and the kernel had no confinement tools to offer anything else back then. Snap’s confinement model answers a real problem.
What I couldn’t square was the experience. And the closest way I can describe it is mechanical. Picture someone dropping a modern, fuel-injected engine into an old ute and leaving everything else alone: the original gearbox, the original diff, the original brakes, the wiring loom held together with electrical tape. The engine is genuinely better. Nothing it’s bolted to was rated for it. So you get a car that’s faster in a straight line and worse at everything else, and every breakdown happens at a join.
That’s where my snap failures happened. The Flutter snap shipped GLib 2.64 frozen at core20 while a plugin pulled in the host’s GLib 2.88, and the build died at the link step. Obsidian’s classic snap ran a desktop-integration script that broke against the GNOME stack in 26.04. Slack’s strictly confined snap hit AppArmor and seccomp denials after the upgrade. None of those failed inside the snap. They failed at the seam, where a self-contained package had to cooperate with a dpkg-managed host it had no control over, and that host kept moving underneath it.
Seager said something on the show that reads, to me, as Canonical admitting the same thing from the inside:
“The things that snaps are good at, they’re very, very good at. And the things they’re not good at are not existential limitations. They’re things that we have yet to implement. And I think one of the reasons we haven’t implemented them is because it hasn’t been the goal to make it the default.”
In other words: the engine was never the problem. Nobody had been told to replace the gearbox.
What the Full Swap Looks Like
Ubuntu Core Desktop is the whole-vehicle answer. Everything is a snap: the bootloader, the kernel, the desktop environment, the daemons, the apps. The base is read-only, updates are transactional and roll back on failure, and there’s no mutable dpkg layer underneath for anything to drift against.
Seager was candid about where the 2023 preview went wrong. It was “lifted” onto the current core26 base, but in his words it “jams the whole of GNOME into a single snap”, which defeats the point. The next few months go into deciding how a desktop actually decomposes: whether PipeWire and WirePlumber share a snap, where libcamera lives, how a login manager like GDM or SDDM gets the permissions it needs. GDM is confined in the current images only with patches to snapd that haven’t gone upstream yet. Fair enough, and it’s a long way from finished.
Three things set this apart from the immutable desktops I’d already looked at.
No rebuild-and-reboot for every update. On ostree and bootc systems like Fedora Silverblue, changing the base usually means a new image and a reboot. On Core you refresh a snap in place, and the kernel can be live-patched.
Composability. You can sit on a 26.04 base and point the desktop at the GNOME track from 28.04, or pull in a newer libcamera so a camera module released after your LTS actually works, without what Seager called a “Frankenbuntu”. Hardware makers could do the same in their factory images. If you’ve ever installed an LTS 18 months into its life on a laptop that’s newer than the release, you’ll know the pain.
Declarative images. A new tool called Imagecraft builds a custom Core Desktop image from roughly a 100-line YAML file. Seager’s own comparison was “almost in NixOS territory”, and as the person who never ran his NixOS test, I noticed.
Then there’s KDE. When u/nhaines replied to the earlier post, he said Core Desktop was being built so that flavours and community members could swap in their own desktop snaps, not just so Canonical could offer a menu. Seager confirmed it: Canonical is paying enioka Haute Couture, a company deeply involved in KDE neon, to build a KDE track alongside the GNOME one from day one, so the team can’t make choices that lock the system to a single desktop. The developer preview releases on GitHub already include KDE images.
The Security Case, Restated
On security, Seager made the argument I’d have made, only more sharply. On traditional Ubuntu, he said, “the file system is kind of floppy. Every process can kind of access everything”, with some file permissions and AppArmor rules layered on top. You can bolt measured boot, verified boot and confidential computing onto that, but you’re always working against the base.
His sharpest example was AI coding agents. “It is only a matter of time,” he said, before “very influential people” have their credentials leaked “because an agent did something silly.” He runs a browser, a chat client and a terminal on the host and does everything else in an LXD container or a VM. On Core Desktop, users simply wouldn’t have the option of installing an agent with unrestricted access to their home directory. I don’t buy the AI hype, but I don’t need to for this one: any tool that runs code on your behalf with your credentials in reach is a risk, and the default on most Linux desktops today is that it gets everything.
Two pieces of the machinery already exist. Permissions prompting works at the syscall level, across the kernel, AppArmor and snapd, so apps don’t need modifying to use it. It arrived in 24.10 for home directory access, added the camera in 25.10 and the microphone in 26.04. It’s still opt-in and labelled experimental, which is fair for something Seager calls key to Core’s success. And Ubuntu Core 26, released in May for IoT and edge devices, already ships TPM-backed full disk encryption with sealed keys in the LUKS2 header and up to 15 years of security maintenance. The pieces are proven on embedded hardware. The desktop is where they still have to meet.
The Escape Hatch
A small aside, because it was a proper TIL moment for me. I hadn’t come across Canonical Workshop before Seager mentioned it, even though it launched in May. A single YAML file defines a reproducible development environment that runs in an unprivileged LXD system container. You build it from reusable SDKs (Ollama, OpenCode, CUDA and ROCm are among the examples), and an interface system borrowed from snapd controls what reaches the host: mounts, devices, the SSH agent, a GUI. Seager said it started as a way to stop sprawling IoT board-vendor SDKs from spilling all over a developer’s machine, which is a problem I remember well from my own Snappy Core experiments in 2015. Canonical engineering manager Dmitry Lyfar summed up the design goal in a line I’d frame and hang over most developer desks: “Ease of use for developers shouldn’t mean ease of access for AI agents.”
On Core Desktop, Workshop becomes the compatibility story. Seager described it as “Windows Subsystem for Linux with the graphics bit”: an app that isn’t a snap runs in a container, and its window appears on the Core desktop as though it were native. He’s been running Firefox that way, wired up through a D-Bus proxy and PipeWire, with notifications, the camera and even Web Serial working. You could, he pointed out, install a Flatpak inside a Workshop and use it the same way.
Credit where it’s due: this is the most honest part of the whole plan. Seager said outright that it’s “no good for us to go out in the world when none of the apps are snaps” and expect people to stay. An escape hatch admits the catalogue isn’t there yet, rather than pretending it is.
Two caveats, though. Workshop itself is currently a classic snap, which means it can’t run on Ubuntu Core as it stands. Strict confinement is promised “in the coming weeks”. And Flatpak getting in as a guest inside a container is a clever way of making it work, but it doesn’t answer what my earlier post actually argued: that Fedora, openSUSE and Debian have all converged on Flatpak for desktop apps, and Ubuntu is the only one asking developers to support a second format. Canonical’s bet is that confinement, automatic updates and usage metrics will be so compelling that vendors choose snaps anyway. That may happen. Nothing announced so far makes it inevitable.
What the Interview Didn’t Touch
Back to the three asks from July.
Commit to a date, or concede the layer. Answered. Images alongside 28.04, a stretch goal for 30.04, and Seager’s own caveat on how aggressive that is. I’ll take a stated target with a public caveat over “in due course” every time.
Stop the silent substitution. Not addressed. apt install cheese on 26.04 still hands you a snap without warning, and nothing in the Core Desktop plan changes the traditional desktop that most of us will be on for years yet. Seager was emphatic that “Ubuntu, as you know it today, is not going anywhere”, which is reassuring, and also means the seam I keep tripping over stays exactly where it is for everyone who doesn’t switch.
Open the store, or stop calling it open. Not addressed either. When asked about infrastructure, Seager acknowledged “our fair share of infrastructure difficulties”, some caused by people deliberately flooding the store with traffic and some Canonical’s own, and said more points of presence are coming. He described a store that has grown into the backend for snaps, charms, images and SDKs. Growing isn’t the same as opening. A Core Desktop where every single component arrives through one closed, Canonical-run store makes that question bigger, not smaller. The community replies on Seager’s announcement were already pointing at it from the packager side: one longtime snap publisher described the build backend as “slow or unreliable”, and the CUPS maintainer reported RISC-V builds taking around four hours and frequently timing out, which isn’t where you want to be when you’re pushing a security fix.
The history from the earlier post still applies. I bought a Meizu MX4 in 2015 to run Ubuntu Touch, and in 2017 Mark Shuttleworth called an all-snap desktop a vision for “a very distant future”. The difference now is concrete: a named team, a public restart post, boot-ready images on GitHub, a partner on the KDE side and a release number. That’s a lot more than I had to go on in 2015.
Not on the Workhorse (Yet)
So here’s where I land.
The NixOS test repo is going in the bin. It was never enough of a priority to run, and if Canonical delivers even half of this, Core Desktop gives my interest in immutable desktops a far more likely home, on the system I already live on.
I’m also not going to run Core Desktop on my work machine any time soon. The current releases are labelled “DANGEROUS developer preview” in capital letters, with unasserted snaps that can never be refreshed, and that’s the right label for where they are. I stick with LTS releases for a reason: I need to get work done on this machine, not debug it, and that isn’t changing. Core Desktop gets promoted to the main machine when a Core image ships alongside an LTS, 28.04 at the earliest, once the people who enjoy the hoist have shaken the worst of it out.
That doesn’t mean ignoring it until then. I’ll let the real bleeding edge pass, but once the dust settles a little, some of the time I’d set aside for NixOS can go into a spare machine that isn’t my daily workhorse, to get a feel for Core Desktop and ease myself in. Getting a bit of grease on my hands before it matters seems the right way to arrive at 28.04.
A word on Seager himself. Across the interview and his own writing, he comes across as a pragmatic engineer with a good dose of common sense: candid about what’s broken, specific about what comes next, and quick to call his own timeline aggressive before anyone else could. On that evidence he’s a very good hire for this role at Canonical, and I wish him all the best with the work ahead.
The engine was never the problem. Snap on traditional Ubuntu was a modern engine in an old chassis, and every breakdown happened at a join. This time Canonical is replacing the gearbox, the diff and the wiring loom as well. I’ll judge it when it’s registered and on the road, not while it’s still up on the hoist. But for the first time in a decade, I believe they’re building the whole new car.
Thanks to Jon Seager and the LINUX Unplugged crew (Chris Fisher, Wes Payne and Brent Gervais) for an interview that went past the talking points, and to u/nhaines, whose reply to the earlier post turned out to be a preview of the KDE track.
Sources
- LINUX Unplugged. 692: Ubuntu’s Core Reset, 8 November 2026 (interview with Jon Seager, 16:47 to 43:46)
- Jon Seager. Accelerating Ubuntu Core Desktop, 27 October 2026
- Jon Seager. The Immutable Linux Paradox, September 2025
- Canonical. Ubuntu Core Desktop developer preview releases, GitHub, November 2026
Related reading on this site
- The Ubuntu Lovers’ Blues, the July post whose three asks this one revisits
- Escaping the Sandbox: Fixing the Zoom Camera on Ubuntu 24.04 and 26.04, the first confinement failure I wrote up
Comments
Be the first to comment! Reply to this post from your Mastodon/Fediverse or Bluesky account, or mention this post's URL in your reply. Your comment will appear here automatically via webmention.
Follow this blog on Mastodon at @gaggl.com@web.brid.gy or on Bluesky at @gaggl.com