Linux App Release Roundup (May 2026)

May 2026 delivered a sizeable set of Linux software updates, including the set I’ve rounded up for your reading pleasure in this post.  The month also saw a buffet of big browser updates, including Firefox 151 with new-look new tab page, Vivaldi 8.0 with a new-look generally and a new public beta of Kagi’s Orion. Elsewhere, Ubuntu 26.04 LTS support was added to VMware Workstation (and Fusion for macOS), while open-source system cleaner BleachBit debuted a TUI for interactive command-line based spring cleaning. Below, I run through a crop of other Linux app releases that landed in May and caught my eye. […]

You’re reading Linux App Release Roundup (May 2026), a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingLinux App Release Roundup (May 2026)

NixOS 26.05 ‘Yarara’ Released with Systemd Initrd by Default and Major Infrastructure Updates

NixOS 26.05 ‘Yarara’ Released with Systemd Initrd by Default and Major Infrastructure Updates

The NixOS project has officially released NixOS 26.05, codenamed “Yarara,” continuing the distribution’s unique approach to Linux system management through declarative configuration, atomic upgrades, and reproducible deployments. The release introduces several important platform-level changes, modernized infrastructure components, and continued refinement of the Nix ecosystem.

As one of the most distinctive Linux distributions available today, NixOS continues attracting developers, DevOps engineers, and advanced Linux users who value predictable system behavior and highly reproducible environments.

What Makes NixOS Different?

Unlike traditional Linux distributions that install packages directly into shared system locations, NixOS is built around the Nix package manager, which stores software in isolated, versioned paths and generates complete system configurations declaratively.

This architecture provides several advantages:

  • Atomic system upgrades
  • Reliable rollback capabilities
  • Reproducible environments
  • Easier infrastructure automation
  • Reduced dependency conflicts

These features have helped NixOS gain popularity among developers managing complex systems and cloud infrastructure.

Systemd-Based Initrd Becomes the Default

One of the most significant changes in NixOS 26.05 is the move to a systemd-based Stage 1 initrd by default. The older scripted implementation is now deprecated and scheduled for removal in NixOS 26.11.

The initrd (initial RAM disk) is responsible for preparing the system during early boot before the main operating system loads.

According to the release notes:

  • Systemd now handles Stage 1 initialization by default
  • The previous scripted implementation remains temporarily available
  • Users can still revert using boot.initrd.systemd.enable = false
  • Long-term migration toward the systemd-based approach is encouraged

This change is expected to improve consistency and simplify maintenance across modern NixOS deployments.

Continuing the Twice-Yearly Release Cycle

NixOS continues its established release cadence of publishing stable versions twice per year—typically around May and November. The 26.05 “Yarara” release follows the previous 25.11 “Xantusia” release and continues the project’s steady development rhythm.

The 26.05 development cycle involved extensive staging, package testing, and release management work coordinated through the NixOS community.

Large-Scale Package and Infrastructure Updates

Like previous NixOS releases, 26.05 includes a massive collection of package updates across the software ecosystem.

Continue ReadingNixOS 26.05 ‘Yarara’ Released with Systemd Initrd by Default and Major Infrastructure Updates

GNOME 51 Development Officially Begins as ‘A Coruña’ Cycle Gets Underway

GNOME 51 Development Officially Begins as ‘A Coruña’ Cycle Gets Underway

The GNOME Project has officially opened the development cycle for GNOME 51, the next major release of one of Linux’s most widely used desktop environments. Following the recent launch of GNOME 50 “Tokyo,” developers are already shifting focus toward the next chapter of the desktop’s evolution, which will carry the codename “A Coruña.”

While it’s still very early in the process, the release schedule is now taking shape, giving Linux users and developers an early look at what to expect over the coming months.

GNOME 51 “A Coruña” Is Now in Development

The new release is named A Coruña, after the Spanish city that will host GUADEC 2026, the annual GNOME Users and Developers European Conference. The event serves as one of the most important gatherings for GNOME contributors, where future desktop plans, technologies, and development priorities are discussed.

As soon as GNOME 50 was finalized, development work for GNOME 51 officially began, continuing GNOME’s well-established six-month release cadence.

Release Schedule Already Published

The GNOME team has outlined the preliminary roadmap for the GNOME 51 cycle.

Current milestone dates include:

  • GNOME 51 Alpha: June 27, 2026
  • GNOME 51 Beta: August 1, 2026
  • GNOME 51 Release Candidate (RC): August 29, 2026
  • GNOME 51 Final Release: September 16, 2026

These milestones provide time for:

  • Feature integration
  • Public testing
  • Bug fixing
  • Performance optimization
  • Final stabilization before release

As always, dates may shift slightly depending on development progress.

Still Too Early for Major Feature Announcements

Because the development cycle has only just started, GNOME developers have not yet revealed a finalized feature list. Most major design discussions and merge requests are still in their early stages.

However, several areas are already attracting attention.

Wayland Improvements Are Likely a Major Focus

One of the biggest transitions in recent GNOME history happened with GNOME 50, which completed the project’s move away from X11 by removing remaining X.Org support from the desktop environment.

Because GNOME is now fully committed to Wayland, many observers expect GNOME 51 to focus heavily on:

Continue ReadingGNOME 51 Development Officially Begins as ‘A Coruña’ Cycle Gets Underway

Ubuntu 26.10 Snapshot 1 is now available to download

Stonking StingrayCanonical has released the first monthly snapshot of Ubuntu 26.10 ‘Stonking Stingray’. This is the first of 4 planned testing builds in the lead up to the final, stable release of Ubuntu 26.10 on 15 October, 2026. Utkarsh Gupta announced the release on the Ubuntu developer mailing list, noting that a couple of images are missing from the first snapshot but will return for Snapshot 2. Ubuntu monthly snapshots are not alpha builds. They exist as a way for Ubuntu’s engineers to fine-tune new, automated build processes. Snapshots are useful jump-on points that help users test the next release, but […]

You’re reading Ubuntu 26.10 Snapshot 1 is now available to download, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingUbuntu 26.10 Snapshot 1 is now available to download

Canonical takes over Flutter desktop maintenance

Google announced at Google I/O 2026 that Canonical is the new lead maintainer and ‘strategic steward’ of Flutter desktop for Windows, macOS and Linux. The news was shared in the ‘What’s new in Flutter’ presentation “[The Flutter] desktop experience has reached a new level of maturity this year, driven by our incredible engineering partnership with Canonical, the publisher of Ubuntu”, says Kate Lovett, Engineer Manager on the Flutter Framework team at Google. “This progress is fuelled by Canonical’s dedication to ensuring that Flutter delivers on every desktop” she adds. Canonical made Flutter its ‘default choice’ for developing new Ubuntu apps […]

You’re reading Canonical takes over Flutter desktop maintenance, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingCanonical takes over Flutter desktop maintenance

Canonical’s Workshop: sandboxed, reproducible dev environments

Workshop by Canonical.Canonical has released Workshop, a new open-source tool to create reproducible development environments with a single command. Using YAML files, the same development setup can be reproduced across different hardware and devices, reducing dependency headaches and configuration drift. Environments in Workshop are built from SDKs (packages that install languages, frameworks and tools). Most of these come from the SDK Store, which supports versioned channels similar to the Snap Store so that projects can define specific SDK versions to use. Canonical offers SDKs for Ollama, OpenCode, NVIDIA CUDA and AMD ROCm at launch, but users can create and define project-specific SDKs […]

You’re reading Canonical’s Workshop: sandboxed, reproducible dev environments, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingCanonical’s Workshop: sandboxed, reproducible dev environments