System76's COSMIC desktop project updated its contribution rules on October 2, 2026, and the change is blunt: pull requests that include any LLM-generated content — source code, comments, or even PR descriptions — will no longer be accepted.

The new policy goes further than simple disclosure. It's an outright ban. Contributors are now required to confirm that nothing in their submission was generated by a large language model before a pull request can be merged.

Why the Ban?

COSMIC lead developer Jeremy Soller of System76 explained the reasoning publicly: the project was being swamped. LLMs have made it trivially easy for first-time contributors to generate plausible-looking code and submit it — but plausible-looking is not the same as correct, aligned with the project's architecture, or planned by the maintainers.

According to Soller, the flood of LLM-generated submissions was "unplanned and rarely accepted," but reviewing them placed a real burden on the small core team. The volume was straining maintainers to the point of unsustainability.

A Pattern Across Open Source

COSMIC isn't the first open source project to encounter this problem, but it may be one of the most prominent to draw a hard line. The project is written in Rust, targets a technically demanding domain — a full Wayland-based desktop environment built from scratch — and has a lean maintainer team. All three factors make low-quality submissions especially costly to process.

Other projects have adopted disclosure requirements or AI-contribution labels. COSMIC's approach is more aggressive: no LLM output, full stop. The policy applies to code, inline comments, and the PR description itself.

One Exception

The ban doesn't extend to the cosmic-flatpak repository, where upstream projects manage their own Flatpak manifests. The COSMIC team reviews those primarily for sandboxing compliance, making the context different enough to warrant separate treatment.

What This Signals

This is a real tension playing out across open source right now. AI tools make contribution easier — but the review cost doesn't disappear just because the code was generated cheaply. If anything, low-effort AI submissions shift cost from the contributor to the maintainer. COSMIC's ban is one data point on how projects with limited bandwidth plan to navigate that tradeoff: drawing a bright line and enforcing it, rather than trying to evaluate AI-generated code case by case.

Ubuntu's newest beta, codenamed "Stonking Stingray," landed on October 1st, 2026 — a few days behind schedule due to infrastructure issues, but worth the wait. "Stonking" is British slang for something impressively large or excellent, a fitting name for a release that ships several meaningful upgrades.

What's New

The headliner is a complete migration to Rust coreutils via the uutils project. Every standard Unix utility you've long relied on — ls, cp, cat, sort — now runs on a memory-safe Rust implementation by default. For most users this will be invisible; for system security, it's a meaningful shift that eliminates an entire category of memory-safety bugs from the base layer.

Ubuntu 26.10 also ships Linux 7.3 (still in release-candidate phase, but included for beta testing), GNOME 51 — the same desktop that debuted in Fedora 45 with passkey login and offline maps — and Mesa 26.2 for improved graphics driver support. The session bus switches from dbus-daemon to dbus-broker for better performance and reliability. WSL and cloud images are part of the beta cycle as well.

Release Schedule

According to the official release schedule, the Release Candidate lands October 8th, and the final release of Ubuntu 26.10 is set for October 15th, 2026. The Canonical team describes the beta as "reasonably free of showstopper image build or installer bugs" — solid enough to test in a VM, not yet recommended as a daily driver.

Why It Matters

26.10 is an interim release, not an LTS. But it's the last non-LTS before the 28.04 LTS cycle, making it a preview of where Canonical is taking Ubuntu for the next several years. The Rust coreutils landing here as stable defaults signals that the 28.04 LTS will almost certainly ship them to hundreds of millions of users.

If you're on Ubuntu 24.04 LTS or 26.04.1 "Resolute Raccoon," this beta won't touch your system — but it's worth watching. Download the Ubuntu 26.10 beta images and file bugs now if you want to help shape what ships in two weeks.

Canonical quietly flipped the switch on September 29, 2026: Ubuntu 24.04 LTS users can now officially upgrade to Ubuntu 26.04.1 LTS, codenamed "Resolute Raccoon," directly from the desktop. Linuxiac confirmed the upgrade path is live, with no command-line workarounds needed.

Why It Took Until the Point Release

Canonical traditionally holds back the LTS-to-LTS upgrade prompt until the first point release (.1). The delay allows the most critical post-launch bugs to get patched before exposing the broader LTS audience—who tend to be on stable, production systems—to the new release. Ubuntu 26.04.1 already incorporates all security patches, bug fixes, and package updates shipped since April's initial launch, making it a meaningfully more stable upgrade target than 26.04.0 was.

How to Upgrade

Desktop users on Ubuntu 24.04 will start seeing an upgrade notification through Software Updater automatically. The prompt reads: "Ubuntu 26.04.1 LTS is now available (you have 24.04)", with a single Upgrade button. If you don't want to wait for the prompt, you can trigger the upgrade manually:

sudo do-release-upgrade

Before starting, Canonical recommends following these pre-upgrade steps: back up important files, run sudo apt update && sudo apt upgrade to make sure 24.04 is fully current, and ensure the system has several gigabytes of free disk space available.

What's in Ubuntu 26.04 LTS

Ubuntu 26.04 "Resolute Raccoon" ships with GNOME 48, Linux kernel 6.14, improved Snap performance, and a refreshed installer experience. Standard LTS support runs through May 2031, with extended security maintenance available to Ubuntu Pro subscribers through 2036.

Gradual Rollout

Canonical is pushing the upgrade prompt out progressively over the coming days, so if you don't see it immediately, that's by design—not a sign that anything is wrong. This phased approach lets Canonical monitor upgrade telemetry and catch any widespread issues before they reach the full 24.04 LTS user base.

For Ubuntu 24.04 users who've been waiting for a stable, officially-blessed path forward, that path is open now.

System76's COSMIC desktop environment — the Rust-built, System76-sponsored alternative to GNOME that ships with Pop!_OS — released version 1.9 on September 24, 2026. The update is incremental by design: COSMIC is still working toward a stable baseline, so each release focuses on closing specific gaps rather than introducing sweeping architectural changes.

This release closes two visible ones.

COSMIC Viewer is the desktop's new native image viewer. Phoronix's coverage of the release notes that it handles a wide range of image formats and includes built-in editing capabilities — making it a practical replacement for the grab-bag of third-party image tools users had been relying on. For a desktop that aims to ship as a complete, coherent system rather than a shell with plugins, shipping a native image viewer matters.

COSMIC OSK is a new on-screen keyboard that supports both touch and gamepad input. This extends COSMIC's usability to tablet-like configurations and couch setups that were previously awkward without a physical keyboard. Gamepad input support in particular is a nod toward the Steam Deck-adjacent use cases that the Pop!_OS user base skews toward.

The release also revamps the COSMIC Store to display developer attribution more prominently for each app and applet. It's a small UX improvement, but one that signals attention to the details that make a software ecosystem feel trustworthy rather than anonymous.

Pop!_OS 24.04 LTS users already have the update available through the system updater. Rolling-release distributions — Arch, openSUSE Tumbleweed, CachyOS — should see COSMIC 1.9 packages land in their repositories shortly after the announcement.

COSMIC's development cadence has been consistent. The team ships frequently, keeps each release focused on specific goals, and communicates clearly about what's in and what isn't. The desktop isn't finished — there are still rough edges, apps that don't exist yet, and integration work ahead — but 1.9 is another concrete step toward something that looks increasingly like a complete, independent Linux desktop, not just a promising experiment.

The bigger picture: COSMIC represents a genuine alternative approach to building a Linux desktop. Where most desktop environments build on GTK or Qt and C-family languages, COSMIC is written entirely in Rust and uses a custom widget toolkit (iced). That's a significant long-term investment by System76, and releases like 1.9 are the evidence that it's paying off incrementally. Linuxiac's coverage has a solid rundown of the full changelog if you want the details beyond the headline features.

Incus 7.5 shipped on September 25, 2026, adding a pair of capabilities that address two of the most requested gaps in the project's feature set: live instance migration between projects and a more flexible OVN networking model.

Live project migration: Until now, moving a container or virtual machine from one Incus project to another required stopping the instance, moving it, and restarting. That disruption is gone in 7.5. Instances can now be moved between projects while running, which changes how operators think about resource reorganization and capacity planning — no more scheduling maintenance windows for what should be a bookkeeping operation.

OVN child networks: The network side of the release is equally significant. Incus 7.5 introduces OVN child networks, which allow multiple internal subnets to share a single logical router, uplink, external address pool, and peering configuration. Each child network still maintains its own subnet, DHCP settings, DNS records, ACLs, and instance ports — and NAT can be independently configured per child. The practical effect is that large multi-tenant environments can consolidate their network topology without sacrificing per-tenant isolation. To support the updated OVN model, the minimum required versions are now Open vSwitch 3.3.0 and OVN 24.03.0.

Security fixes: The release addresses 11 security vulnerabilities — an unusually high count for a single point release. The quantity signals that users on earlier 7.x releases should treat the upgrade as urgent.

Incus 7.5 also extends VM agent support, adds new performance metrics for monitoring, and carries a range of smaller fixes. The project continues its monthly cadence, positioning 7.5 as the stable platform ahead of what the team has signaled will be a feature-heavy 8.0 series.

The release is available immediately through the LinuxContainers project.

Systemd 262 landed on September 22, 2026, and carries a broader set of changes than any release in recent memory. The headline is unusual for an init system release: an AI/LLM canary, a mechanism designed to help maintainers identify code contributions generated by AI that haven't been adequately reviewed by a human developer before merging.

The canary doesn't block anything automatically — it's a disclosure and detection aid, not a gate. But as AI-assisted development becomes more common in critical infrastructure projects, systemd being one of the first high-stakes open source components to address this problem directly is significant. The project's maintainers have been explicit that unreviewed AI code is a liability, and this builds accountability into the workflow.

Beyond the canary, systemd 262 makes structural improvements to containers, security, and service management.

Containers and minimal environments: Systemd can now be compiled as a single statically linked PID 1 binary, making it viable for very small container images where installing a full unit file tree isn't practical. A built-in fallback set of unit files means the manager can operate from memory when disk-based unit files can't be loaded — useful in locked-down container scenarios.

Hardware-rooted security: Intel TDX (Trust Domain Extensions) joins AMD SEV-SNP as a supported confidential computing platform. TPM integration deepens with Storage Root Key pinning and Argon2id PIN enrollment for systemd-cryptenroll, giving disk encryption setups stronger hardware-backed authentication options.

Service reliability: A new RestartRandomizedDelaySec= directive lets services delay their automatic restart by a random interval, which prevents the thundering-herd problem where dozens of failing services all restart simultaneously after a shared failure event. The LUOSession= option connects service units to Live Update Orchestrator sessions, enabling coordinated live service updates without a reboot.

The release also adds OpenSSL 4 support and a range of networking and storage improvements. For Linux distributions shipping systemd — which is most of them — this release's combination of security hardening and AI code provenance tooling sets a template other projects will likely follow.

Systemd 262 is available now; most major distributions will begin staging it in the coming weeks.

System76's COSMIC desktop is moving fast. Just 13 days after releasing version 1.8, the team shipped COSMIC Epoch 1.9 on September 23, 2026, adding two new first-party applications and a redesigned app store. The pace suggests the team is operating in a rapid iteration mode that's unusual for a desktop environment project.

COSMIC Viewer: A Native Image Viewer, Finally

The headline addition is COSMIC Viewer, a native image viewer that supports a wide range of formats and includes built-in basic editing capabilities. Until now, COSMIC lacked a first-party image viewer, which was a notable gap for a desktop claiming to be a complete environment. COSMIC Viewer fills that gap with a clean Rust-native implementation that fits the visual language of the rest of the desktop.

The second new app is COSMIC OSK, an on-screen keyboard designed for both touch and gamepad input. This is particularly significant for COSMIC's ambitions: Pop!_OS, the distro from System76 that ships COSMIC by default, has been expanding toward tablet and touchscreen use cases. A native, first-class on-screen keyboard that works above the lock screen makes COSMIC meaningfully more viable as a tablet desktop. The lock screen can now display the OSK on top of it directly, which is a prerequisite for touch-only login flows.

Settings and Store Updates

The Settings app picks up several useful additions: the About page now shows the installed COSMIC version, there are new configuration options for the on-screen keyboard, WireGuard-related issues are resolved, and you can now opt to display the day of the week in the clock. Small things, but the kind of polish that accumulates into a usable system.

The COSMIC Store receives a visual redesign that adds developer attribution — each application or applet now shows who made it. This is a trust signal that matters as third-party COSMIC applets proliferate. Users can see at a glance whether they're installing something from a known project or an unknown contributor.

systemd-homed and Files Fixes

COSMIC Greeter gains optional support for systemd-homed, systemd's system for portable, encrypted home directories. This is a niche but important feature for security-conscious users who want their home directory encrypted at rest and tied to user authentication rather than full-disk encryption.

COSMIC Files gets several reliability fixes: drag-selection behavior is corrected, Windows .exe files now display proper icons, sorting preferences persist across file dialogs, and Shift-based context menus work correctly. The compositor also gains support for showing layer-shell applications — including the new on-screen keyboard — on top of the lock screen.

COSMIC 1.9 is available on GitHub and ships with Pop!_OS builds. Given System76's current release cadence, version 1.10 is presumably a week or two away.

GNOME 51, codenamed "A Coruña," shipped its stable release on September 16, 2026. The update lands two days ahead of today and brings several headline features — most notably passkey support for the login screen, offline maps in the Maps application, and hand-drawn PDF signatures — on top of a round of polish aimed at making everyday desktop interactions feel more fluid.

Passkey Login Is Finally Here

The most security-forward addition in GNOME 51 is FIDO2 passkey authentication at the login screen. Users can now authenticate with hardware security keys or platform authenticators directly from the GNOME display manager, bypassing passwords entirely. This brings GNOME in line with where the broader web ecosystem has been heading for several years and makes the desktop login flow meaningfully more secure against credential-stuffing and phishing. The feature works alongside existing PIN and password options rather than replacing them.

Offline Maps and Better Documents

GNOME Maps gains offline map support and live transit information, meaning you can download areas for use without a network connection and see real-time public transport data when you're online. The Papers document viewer adds hand-drawn signature support — useful for anyone who regularly signs PDFs without wanting to leave the desktop environment for an external tool.

Smoother Animations and a Reduced Motion Option

Under the hood, GNOME 51 includes frame scheduling changes that improve how animations and scrolling feel when the system is under load. Previously, a heavy background process could cause the UI to stutter noticeably; the new scheduling logic keeps interface animations more consistent. A new Reduced Motion toggle in Accessibility settings lets users who are sensitive to movement dial back animations system-wide — a feature that's been present in macOS and iOS for years and has been a frequent request from the Linux accessibility community.

NVIDIA Legacy Hardware Loses Proprietary Driver Support

GNOME 51 removes the legacy NVIDIA driver paths that older cards like the GeForce GTX 700 series relied on. Those GPUs fall back to the Nouveau open-source driver under GNOME 51. For most workflows Nouveau performs adequately, but users with older NVIDIA hardware doing GPU-intensive work should verify compatibility before upgrading. The move cleans up a significant maintenance burden in the GNOME codebase.

When Will You Get It?

GNOME 51 will ship in Fedora 45, currently in beta, and in Ubuntu 26.10 which is due October 15. Users on long-term-support distributions like Ubuntu 24.04 or 26.04 won't receive it through normal channels. Source tarballs are available now at download.gnome.org for those building from source. Rolling-release distributions like Arch and openSUSE Tumbleweed will pick it up over the coming days through normal package updates.

GNOME 51 is a release that rewards existing users more than it converts newcomers — but passkey support alone is the kind of security-forward change that makes it worth tracking for anyone who runs a GNOME desktop.

The Fedora Project shipped Fedora Linux 45 Beta on September 15, 2026, dropping a feature-dense preview of what's coming in late October. Beyond the standard version bumps, Fedora 45 carries several structural changes that rethink how the system handles consoles, secrets, and process isolation.

KMSCON Replaces the In-Kernel Console

The most visible low-level change is the switch from fbcon — the aging framebuffer console built into the Linux kernel — to kmscon, a userspace terminal emulator that drives the display via kernel mode setting directly. The result is a more capable virtual terminal with better font rendering, proper Unicode support, and smoother integration with the modern graphics stack. If you've ever booted into garbled text or hit inconsistencies with fbcon on modern GPU drivers, this is a direct structural fix rather than a workaround.

oo7 Unifies Secret Management

One of the more significant under-the-hood changes: Fedora 45 drops both GNOME Keyring and KWallet in favor of oo7, a single unified Secrets Service implementation that works consistently across GNOME, KDE Plasma, and other desktop environments. Historically, applications had to guess which secret manager was running or cope with duplicated, conflicting credential stores. oo7 replaces both with one standardized backend — a long-overdue consolidation.

ptrace Restricted by Default

Unprivileged ptrace — the system call that lets one process inspect or inject code into another — is now restricted system-wide by default. This closes a class of attacks where malware could silently attach to running processes without root. When debugging tools are installed, the restriction automatically relaxes to preserve developer workflow, so the security default costs developers nothing in practice.

Toolchain and Desktop Updates

The toolchain refresh is thorough: Python 3.15, Go 1.27, GCC 16.2, Glibc 2.44, and LLVM 23 all ship with Fedora 45. Desktop environments include GNOME 51 on the Workstation spin and KDE Plasma 6.7 on the KDE spin. The Anaconda installer gains Stratis Storage support, and package builds are now expected to be reproducible by default — with a DRM Panic front-end to make kernel crash messages more readable when things go wrong.

What's Next

The final release of Fedora Linux 45 is scheduled for October 20, 2026, with a fallback date of October 27 if blockers remain. Testing feedback from the Beta is the fastest path to a clean launch.

Long-Term Support (LTS) releases of Ubuntu are built to last. Ubuntu 24.04 LTS "Noble Numbat" launched in April 2024 and carries standard security support through May 2029. Point releases — the .1, .2, .3 suffixes — are cumulative snapshots of everything that's landed since launch: security patches, bug fixes, and updated hardware support. They matter most for fresh installs, sparing new deployers from immediately applying months of accumulated updates.

Ubuntu 24.04.5 LTS, released on September 10, 2026, follows that pattern — except its kernel bump is anything but routine for an 18-month-old release.

Linux 7.0 on Noble Numbat

The headline change in 24.04.5 is the Hardware Enablement (HWE) stack shifting to Linux 7.0, the same kernel that shipped with Ubuntu 26.04 LTS "Resolute Raccoon" earlier this year. Ubuntu's HWE mechanism is how the project delivers newer kernel and graphics support to older LTS releases — it lets the underlying OS stay current with new hardware without requiring users to upgrade to a new Ubuntu version.

Alongside the kernel, Ubuntu 24.04.5 LTS bundles the Mesa 26.2 graphics stack, which brings improved driver coverage for recent AMD RDNA 4, Intel Arc Battlemage, and other GPU hardware released in the past year. As OMG Ubuntu explains, both the Linux 7.0 kernel and Mesa 26.2 were already available as an opt-in HWE update for existing Noble Numbat users before today's point release — the ISO just ships with them by default now.

What Doesn't Change

If you're already running Ubuntu 24.04 LTS and value kernel stability over freshness, nothing is forced on you. Systems running the General Availability (GA) kernel stay on the original 6.8 series that shipped with 24.04.0 in April 2024. Enterprise deployments that depend on specific kernel versions for certification or ISV support can continue doing exactly that without any changes.

The support window is also unchanged. Standard security support for Ubuntu 24.04 LTS runs through May 2029, measured from the original April 2024 release. Point releases don't reset the clock.

Should You Make the Switch?

If you're on Ubuntu 24.04 LTS and your hardware is recent enough to benefit from Linux 7.0 or Mesa 26.2 — newer AMD or Intel GPUs, newer laptops with fingerprint readers, newer NVMe controllers — enabling the HWE kernel is worth it. You don't need to reinstall; you can switch on an existing system. Canonical's kernel lifecycle page has the full details on when HWE kernel updates land and what each brings.

If you're doing a fresh Ubuntu 24.04 LTS deployment now, the 24.04.5 ISO is the right one to grab — it saves your first boot from downloading months of accumulated patches. The updated image is available at releases.ubuntu.com/noble/.

It's not a dramatic release. It's a practical one — which is exactly what a point release for a mature LTS should be.

System76 tagged COSMIC Epoch 1.8.0 on September 9, 2026, the latest coordinated snapshot of its Rust-built Linux desktop environment. The release focuses primarily on the compositor — cosmic-comp — with additions that expand input device handling and inter-process clipboard sharing.

What Changed in the Compositor

The headline addition is tablet emulation support, letting the compositor translate trackpad or mouse input into stylus-style signals that drawing and design applications understand as a tablet device. Alongside that, COSMIC Epoch 1.8 adds libei pasteboard sharing, which enables applications and remote input tools to exchange clipboard content through the libei protocol — filling a gap that had left some Wayland-based remote-control and accessibility tools unable to paste reliably into COSMIC sessions.

A new corner radius protocol for rounded window borders was also added, giving application developers a standardized way to declare their preferred corner rounding rather than relying on compositor-side heuristics.

Outside the Compositor

The rest of the release is maintenance and quality-of-life work. Bluetooth device alias handling was improved, reducing the frequency of generic device names appearing where a user-assigned alias should show. The audio source volume slider received a targeted fix. Most notably for shared machines, the greeter now supports multi-factor PAM login chaining — meaning it can handle authentication flows that require a password plus a second factor, such as a TOTP code, without needing a workaround.

According to the release notes on Linux Compatible, the 1.8.0 tag pins more than twenty independently developed COSMIC submodules together in a single tested snapshot — which is what the "Epoch" label means in System76's release model.

Context and Cadence

COSMIC 1.8 arrived two weeks after COSMIC 1.7, maintaining the project's steady cadence of incremental releases. The environment remains in active development, with each Epoch release solidifying stability across the Rust-based stack. The project builds every component — compositor, app launcher, file manager, settings — in Rust, targeting a smaller attack surface and more predictable memory behavior than traditional C-based desktop stacks.

The tablet emulation support is particularly relevant for Pop!_OS users running drawing software. Previous COSMIC releases had limited support for touchpad-as-tablet workflows that tools like Krita and Inkscape support on other compositors. The libei change also has accessibility implications: libei is increasingly used by on-screen keyboards and switch access tools to interact with Wayland desktops, and full pasteboard support removes a friction point for those workflows.

For anyone already running COSMIC, the 1.8 update lands through the usual System76 channels and Pop!_OS repositories.

Arch Linux's monthly ISO snapshot for September 2026 is out, and it ships a meaningful kernel upgrade: Arch Linux 2026.09.01 is the first Arch ISO to default to Linux kernel 7.2.2, a notable jump from the 7.1.5 kernel that shipped in August's image. The new ISO weighs in at 1.5 GB and carries the latest Archinstall 4.4 text-mode installer.

If you're setting up a new Arch installation—or refreshing a virtual machine or test environment—this is the ISO to grab.

What's New in Linux 7.2

Linux 7.2 is not a minor point release. The branch introduced several driver improvements and architecture-level changes that matter particularly for newer and older hardware alike. The Arch team notes that the 7.2 kernel detects hardware components that previous Arch ISOs failed to initialize correctly—a particular win for users on machines that sat in an awkward compatibility gap between 7.0 and 7.1 driver support.

On the AMD side, earlier Linux 7.x releases already folded in DCN 6.0 display driver support, improved Zen 6 scheduler awareness, and overhauls to the KVM subsystem. The 7.2 branch continues that cadence with additional stability fixes across the AMD and Intel stacks. The 9to5Linux writeup on the release highlights that the new ISO should noticeably reduce the "hardware not detected" headaches that occasionally plagued fresh installations on cutting-edge systems.

Archinstall 4.4

The bundled installer has been updated to version 4.4. Archinstall has matured considerably since it became the recommended guided-installation path for new users—it now handles disk encryption, filesystem selection (including Btrfs subvolume layouts), and profile-based desktop environment setup without requiring users to manually partition or configure bootloaders. Version 4.4 includes refinements to the mirror ranking logic and fixes for edge cases in the disk partitioning flow.

For experienced Arch users, Archinstall is of course optional—the ISO boots to a live shell as always, and manual installation via the Arch Wiki remains fully supported. But for users who want a fast, scripted path to a working base system, 4.4 is the smoothest the tool has been.

Download and Verification

The ISO is available from Arch Linux's official download page and worldwide mirrors. The SHA256 checksum for the September 2026 image is be8458032f8105e60ee2a3067f950b6e3c007ee51b38dac50e8b48e765561c91. As always, verify the checksum before writing to a USB drive—Arch mirrors are generally reliable, but it's a two-second check that's worth building into the habit.

Torrent and magnet URI downloads are also available for those who prefer peer-to-peer distribution.

A Note on Rolling Releases

Existing Arch installations don't need to reinstall to get kernel 7.2. A standard pacman -Syu will pull it in as part of the normal rolling update cycle—and for most users running updated systems, it's likely already installed. The monthly ISO release is primarily for new installations and for keeping bootable media current. It's worth updating your Ventoy stick or live USB if you use one for system rescue or deployment.

Arch Linux 2026.09.01 is available now.

For Wayland desktop users who care about both performance and aesthetics, September 5, 2026 brought a notable release: DankMaterialShell 1.6, codenamed "Marble Tabby". The update delivers the biggest performance overhaul in the project's history alongside a visually bold new bar design called Dank Island.

What Is DankMaterialShell?

DankMaterialShell (DMS) is a complete desktop shell for Wayland compositors — it works with niri, Hyprland, MangoWC, Sway, labwc, and others. Unlike a GNOME shell extension, it replaces the entire desktop layer, providing its own bar, launcher, dashboard, notifications, and control center. It draws stylistic inspiration from Material Design while targeting power users who want deep customization without hand-writing compositor config files.

The Performance Numbers

The headline of the 1.6 release is a sweeping performance overhaul. According to the project's own benchmarks, the improvements are substantial across the board:

• IPC calls: 5.2× faster — the communication layer between shell components is dramatically more responsive
• Screenshot operations: up to 8.6× faster — practically instant on modern hardware
• Color picker: 3.9× faster
• Idle memory usage reduced by ~19% — roughly 76 MB saved on a two-monitor test system

These aren't micro-benchmarks on contrived workloads. The IPC speed in particular matters every time a widget updates, a notification lands, or media playback changes state. A 5× improvement there makes the entire shell feel snappier throughout the day.

Dank Island: A New Bar Mode

The most visible addition is Dank Island — a floating bar mode centered on a single interactive island with satellite widgets on each side. The island's content adapts in real time, surfacing notification summaries, media playback controls, and on-screen display feedback. Surfaces like the dashboard and control center can expand directly from the island rather than appearing as separate overlays, keeping interactions compact and coherent.

The aesthetic is deliberately reminiscent of Apple's Dynamic Island, but built on open web technologies (the Dank Linux stack uses modern web tech internally) and designed for a keyboard-and-pointer Wayland workflow rather than a touch interface.

Other Changes in 1.6

GTK3 dynamic theming lands in this release, allowing the shell to recolor GTK apps in sync with the current desktop accent. The greeter has been split into a standalone project, dank-greeter. Versioning is now unified across the full Dank Desktop suite — DMS, dsearch, dgop, dcal, and dgreeter all share the same release number, which simplifies dependency tracking for distribution packagers.

If you run a Wayland compositor and have been on the fence about DMS, 1.6 removes most of the performance objections. A significantly lighter idle footprint combined with a polished new bar makes this a compelling upgrade for anyone invested in the Wayland ecosystem.

CERN runs the Large Hadron Collider. It also runs roughly 2,200 industrial computers and embedded systems spread across 43 square kilometers of accelerator infrastructure, each one connected to about 17,000 physical devices. For most of the last three decades, those machines ran Red Hat Enterprise Linux. Not anymore.

As of this week, CERN's accelerator controls team is migrating the entire fleet to Debian 13, targeting completion by the end of 2026. It's one of the most consequential Linux distribution switches in scientific computing history, and the trigger was surprisingly specific: a compiler flag.

The Straw That Broke the Camel's Back

CERN's relationship with Red Hat is long. The physics organization co-maintained Scientific Linux, a RHEL derivative. It moved to CentOS after RHEL licensing costs made Scientific Linux unsustainable, then watched CentOS's direction shift under IBM ownership. Through all of that, CERN stayed in the Red Hat ecosystem.

What finally pushed them out was RHEL 9's decision to raise its x86-64 microarchitecture baseline to v2 — the -march=x86-64-v2 compiler flag. That flag requires SSE4.2 and POPCNT instruction support, which modern CPUs all have but older embedded boards do not. CERN operates hardware that spans decades. Some of those boards can't be easily replaced. Under RHEL 9's new minimum, they'd need redesigning.

CERN estimated that staying on the Red Hat path would cost roughly CHF 5.4 million, requiring about 11 hardware boards to be redesigned. Debian, by contrast, still builds its amd64 port against the original x86-64 baseline, meaning those legacy boards keep running without modification.

What Debian 13 Gives CERN

The migration isn't just a cost dodge. Debian 13 "Trixie" offers CERN a stable, community-governed platform with long support cycles, no corporate owner who can shift strategy mid-stream, and a package ecosystem large enough to cover CERN's real-time control software stack. It also sidesteps the licensing complexity RHEL introduced when Red Hat tightened source code access in 2023.

The challenges are real, though. CERN's team has documented gaps: no standard tooling for automated package building and publishing, and toolchain incompatibilities with systems that need to support multiple package versions simultaneously. These are solvable — Debian's infrastructure team has been actively engaged — but migrating accelerator control software isn't like updating a web app.

Why This Matters Beyond CERN

CERN isn't a typical enterprise customer. It's an institution that shapes how scientific computing infrastructure is designed globally. When it switches distributions, other national labs, universities, and research institutes pay attention.

The migration is also a data point in a broader trend: institutions that had long accepted Red Hat's terms are reconsidering after the 2023 CentOS source-code restrictions. CERN's public documentation of their rationale gives others a detailed roadmap for making the same call — and a credible answer to the question of what you do with hardware that RHEL's new CPU baseline leaves behind.

The Large Hadron Collider runs on Debian now. That's a sentence that would have sounded implausible five years ago.