Canonical is turning Ubuntu on Arm64 into a “first-class” experience, and it has receipts for the hard parts. In an Ubuntu on Arm summer '26 update on the Ubuntu Discourse, Canonical engineering manager Ravi Kant Sharma outlined progress that spans servers, desktops, and the distribution plumbing. But the story has a very modern tech twist: while Ubuntu leans further into Rust for core utilities and services, it has also run into a practical edge-case problem in the Rust replacement for cp.

Here is the problem, straight from the reported bug: the Rust version of the cp command misinterprets the -L switch. The cp manual says -L, --dereference should “always follow symbolic links in SOURCE.” For now, the team reverted to the classic C-based GNU cp command. That means the headline move is not “Rust is safer” or “everything is fixed.” It is more specific and more useful for operators: even subtle behavioral differences in core Unix commands can break the promise of drop-in replacements, so Canonical is taking the conservative path while it irons out correctness.

The Arm64 push is the other half of the picture, and it is aimed at where money and leverage tend to cluster. Canonical’s recent changes make kernel live-patching on Arm64 part of mainstream Ubuntu 26.04, and also include the IoT-focused immutable Ubuntu Core 26. That framing matters because kernel live-patching is generally a server feature. If you are running Ubuntu on a laptop or desktop, rebooting is inconvenient but straightforward. For fleets, though, live updates can be the difference between acceptable downtime and avoidable operational chaos.

And that fleet logic has a market tailwind behind it. As The Register notes, Arm server sales are now nearly half the market. That is why server support is where Canonical makes most of its money, at least in broad strokes. The company is not just pushing “Arm works.” It is stacking support so that popular end-user workloads can run too. Earlier in June, Canonical announced a native Arm64 snap package of Valve’s Steam client. The package includes x86-32 and x86-64 binaries, relying on the FEX emulation layer, which The Register compares to Apple’s Rosetta 2. FEX development has been funded by Valve for years, and it is expected to play a role in the forthcoming Steam Frame VR headset that Valve announced last year. The point for decision-makers is not headset hype. It is that Canonical is aligning distribution and emulation support with the demand curves of high-engagement apps.

Canonical’s Arm64 runway also extends beyond Qualcomm system-on-chips. There is a Resolute Raccoon “concept image” for CIX P1-based hardware. Devices built around the new CIX Technologies P1 got Linux kernel support a year ago, and Canonical indicates it is used in some Radxa and Orange Pi single-board computers. Even a Framework laptop motherboard is referenced as using it. Layer on top of that momentum and you get a broader ecosystem story: more hardware architectures are gaining the baseline kernel and userland support to make Ubuntu more than a niche port.

If you are thinking about enterprise rollout risk, watch how distribution mechanics are getting rewritten, not just apps. Arm64 packages have been moved to the main Ubuntu download servers on archive.ubuntu.com. Until now, they were hosted on the specialist ports.ubuntu.com servers, alongside other non-x86 versions like PowerPC, RISC-V, and IBM mainframes. This affects how mirrors pull and serve packages worldwide, because the Arm64 packages will now be automatically carried by Ubuntu’s mirror servers around the world. That is not trivial. The Register reports it required changes to scripts and the build pipeline that generate Ubuntu installation images, and it exposed bugs, including an issue in cloud-init.

Now connect that operational reality back to the Rust core utilities thread, because this is where the “why it matters” becomes very real. In April, when Canonical released the current Ubuntu LTS version, The Register reported VP of Engineering Jon Seager promised to “make interim releases crazy again,” with plans including adopting a new Rust Network Time Protocol daemon. At the end of last month, Canonical stepped up to become a Gold Sponsor of the Trifecta Tech Foundation, which develops ntpd-rs as well as sudo-rs. A bug last year in Ubuntu 25.10 caused a security issue tied to sudo-rs, and sudo-rs and ntpd-rs sit in the broader theme of moving system components into Rust implementations. But The Register emphasizes a boundary that matters to readers tracking governance and provenance: Trifecta Tech developed both sudo-rs and ntpd-rs, but it did not create the new Rust coreutils used in recent Ubuntu versions. The new NTP daemon is also independent from the NTPsec Project, which is described as “a secure, hardened, and improved implementation of Network Time Protocol derived from NTP Classic.”

Finally, the strategic stakes for peers are the same whether you are a distro maintainer, a cloud operator, or a platform engineering lead. Canonical is pushing Arm64 support deeper while continuing Rust migration of foundational tooling. The cp -L bug is a warning flare about risk in behavioral equivalence, not just memory safety. For executives, this is a governance and quality-control question: how fast can you ship replacements for core utilities without breaking user assumptions, scripts, or automation? When you are moving architectures, tooling, and distribution pipelines in parallel, the bottleneck is rarely compilation. It is correctness under the weird edge-cases that production systems actually live on.

In other words: Canonical’s Arm64 momentum looks real. The cp reversal is equally real. Together they tell a consistent story about the work: expanding platform reach is hard, and upgrading the “boring” Unix core is harder than it sounds.