COSMIC Epoch 1.8: System76's Rust Desktop Gets a Wayland Compositor Overhaul
On September 9, 2026, System76 tagged COSMIC Epoch 1.8.0 on GitHub, with Phoronix covering the release the next day. It arrived just two weeks after Epoch 1.7, and by System76's own admission it isn't the flashiest update in the project's history. Most of it is fixes, protocol groundwork, and translation updates. But buried in that unglamorous list is a set of changes that matter more than a headline feature would, because they touch the compositor layer that everything else on a COSMIC desktop, including a live wallpaper, has to render through.
If you haven't been following System76's Rust desktop project closely, COSMIC Epoch is worth a quick introduction before getting into what 1.8 actually changes.
What COSMIC Epoch actually is
COSMIC is System76's free and open-source desktop environment, built in Rust and shipped as the default desktop on the company's own Pop!_OS distribution. Its Wayland compositor, cosmic-comp, is written on top of the Smithay compositor library rather than forked from an older project's code, which is the detail System76 leans on when it calls COSMIC the first new Linux desktop in years that doesn't feel like a variation on something that already existed.
COSMIC has spent 2026 moving well past its early alpha reputation. It's the default on Pop!_OS, and it's now also packaged by Fedora, Arch Linux, NixOS, openSUSE Tumbleweed, Gentoo, CachyOS, Garuda, Enterprise Linux 9 and 10, postmarketOS, Slackware, and AerynOS. That's a wide enough spread that a compositor-level release like 1.8 doesn't just affect one distro's users, it ripples across most of the desktop Linux ecosystem that has adopted it.
What's actually new in Epoch 1.8
The centerpiece of 1.8 is a set of changes to cosmic-comp itself. The compositor gains a new corner radius protocol, which lets windows have properly rounded borders handled at the compositor level instead of faked by individual apps, and tablet grab support, which improves how graphics tablets and styluses interact with COSMIC's shell. XWayland windows, the compatibility layer that lets older X11-only apps run under a Wayland session, can now start minimized instead of always popping up on screen. On the settings side, COSMIC Settings picked up the ability to rename connected Bluetooth devices, fixing a small but genuinely annoying gap where paired devices showed up under whatever generic name the hardware itself broadcast.
None of that is dramatic on its own. What makes 1.8 worth paying attention to is the fix list that came with it, because several of those fixes are the kind of thing that decides whether a COSMIC desktop feels solid day to day or keeps tripping over itself.
The bug fixes that matter more than the features
The corner radius protocol introduced its own regression, a screenshot tool crash, which 1.8 fixes in the same release. More significant is a fix that makes cosmic-comp check every display connector when identifying the primary GPU, addressing a real problem on hybrid GPU laptops, the kind with both an integrated chip and a discrete graphics card, where the wrong GPU being treated as primary can mean everything on screen, from window compositing to any GPU-accelerated content, runs on the slower or wrong chip. There's also a fix for the cursor incorrectly magnifying itself while a window was being grabbed and dragged, a corrected audio source volume slider, and multi-factor PAM login chaining added to the greeter for anyone using more than one authentication method to log in.
For anyone gaming on a COSMIC desktop, the fix worth knowing about is a repaired case of sluggish Steam overlay performance inside cosmic-comp. Overlay rendering sits squarely in compositor territory, and a compositor that mishandles it can turn something as simple as opening the Steam overlay mid-game into a stutter. That single line in the changelog says more about how COSMIC is maturing than any new setting does: a young compositor moving from "does it work" to "does it work as smoothly as the desktop it's replacing."
Where COSMIC fits into 2026's Wayland shift
COSMIC's steady 1.x releases are landing in the middle of a broader move across Linux desktops toward Wayland-only sessions, a shift we've tracked as it played out on other desktops this year. GNOME 51, covered in our GNOME 51 "A Coruña" rundown, shipped September 16 with its own compositor-adjacent changes, including a standard background blur API. KDE Plasma is going further: Plasma 6.8, detailed in our KDE Plasma 6.8 piece, drops the X11 session entirely on October 14. We also wrote more broadly about the distro-level version of this shift in our look at Wayland becoming the default across major distros, which is the same underlying trend COSMIC was built for from day one rather than migrating toward.
That context matters because COSMIC never had an X11 session to drop. cosmic-comp was Wayland native from its first line of code, which is part of why a release like 1.8, focused on compositor protocol work rather than a migration story, reads differently than the equivalent GNOME or KDE release notes. COSMIC's competition isn't convincing users to leave X11 behind, it's convincing them a from-scratch Rust compositor can match the polish of desktops with two decades of X11-era muscle memory built into them. Fixes like the Steam overlay stutter and the hybrid GPU connector check are exactly the kind of unglamorous work that closes that gap.
What Epoch 2 is aiming at
System76's public roadmap for the next major line, Epoch 2, is explicitly about performance rather than new user-facing features. The plan centers on a Vulkan renderer for cosmic-comp, a move toward reactive rendering that System76 estimates could cut CPU usage by roughly 60 to 80 percent in typical use, and multi-threaded image decoding paired with parallel GPU image uploads. If that lands as described, it would be a meaningful shift for anything that keeps the compositor busy continuously, wallpapers included, since reactive rendering only redraws what's actually changed on screen instead of repainting everything on a fixed schedule.
For now, Epoch 1.8 is an incremental release, and System76 has said as much itself. But incremental compositor releases are exactly where a desktop's long-term reliability gets built, one fixed connector-detection bug and one corrected corner radius regression at a time.
What this means if you run a live wallpaper on COSMIC
A live wallpaper on Linux lives or dies by compositor behavior. Gloomia runs on Windows, macOS, and Linux, and on a COSMIC desktop, it renders through cosmic-comp the same way any other Wayland client does. That makes changes like the hybrid GPU connector fix directly relevant: if a laptop's discrete GPU wasn't being correctly identified as primary before 1.8, a GPU-rendered wallpaper could have been running on the wrong chip without any obvious sign why performance felt off. The Steam overlay fix points at the same underlying idea from a different angle, on a gaming-oriented desktop, we covered which of Gloomia's own scenes hold up best under sustained GPU load in our gaming desktop live wallpaper roundup, and compositor-level fixes like these are a big part of why that answer can shift release to release.
None of this requires action from a COSMIC user. Distro package managers will pull in Epoch 1.8 on their own schedule, and Gloomia doesn't need any special configuration to run under it. It's simply worth knowing, if a COSMIC desktop feels marginally smoother under a live wallpaper after updating this month, that a specific list of compositor fixes is very likely why.
Frequently asked questions
What is COSMIC Epoch, exactly?
COSMIC Epoch is System76's Rust-based desktop environment and Wayland compositor, built as the default desktop for Pop!_OS. Its compositor, cosmic-comp, is written from scratch on top of the Smithay Wayland library rather than forked from an older desktop's code, which is part of why System76 markets it as the first genuinely new Linux desktop stack in years.
When did COSMIC Epoch 1.8 release, and what does it change?
COSMIC Epoch 1.8.0 was tagged on GitHub on September 9, 2026, with Phoronix covering it the following day. It centers on a compositor overhaul: a new corner radius protocol for rounded window borders, tablet grab support, the ability for XWayland windows to start minimized, and renamed Bluetooth device aliases in COSMIC Settings, alongside a batch of stability fixes.
What bugs did COSMIC Epoch 1.8 actually fix?
Notable fixes include a screenshot tool crash tied to the new corner radius handling, a check across all display connectors so hybrid GPU laptops correctly identify the primary GPU, a fix that stopped the cursor from magnifying itself while a window was being grabbed, a corrected audio source volume slider, and a fix for sluggish Steam overlay performance in cosmic-comp.
Which Linux distributions ship COSMIC?
COSMIC is the default desktop on Pop!_OS, and by mid-2026 it is also packaged by Fedora, Arch Linux, NixOS, openSUSE Tumbleweed, Gentoo, CachyOS, Garuda, Enterprise Linux 9 and 10, postmarketOS, Slackware, and AerynOS, making it one of the more widely distributed newer desktop environments on Linux.
What is planned for COSMIC Epoch 2?
System76's public roadmap for Epoch 2 centers on performance: a Vulkan renderer for the cosmic-comp compositor, reactive rendering aimed at cutting CPU usage by roughly 60 to 80 percent in typical use, and multi-threaded image decoding with parallel GPU image uploads.
Does Gloomia run on COSMIC?
Gloomia supports Windows, macOS, and Linux, and on Linux it runs under the Wayland session that COSMIC provides through cosmic-comp. Compositor-level changes like the ones in Epoch 1.8, including GPU connector detection and corner radius handling, are exactly the kind of low-level plumbing that determines how smoothly any live wallpaper renders on a given desktop.