GNOME’s Release Team put out the beta version of GNOME 51 on August 15, marking the start of the development cycle’s “Freeze” period, where the interface, feature set, and APIs lock down ahead of the stable release. Announced by Abderrahim Kitouni on the project’s Discourse forum, the beta is aimed at developers and testers rather than everyday desktop use, but it does show what’s coming when GNOME 51 ships to the public.
What’s New
This cycle skews toward polish rather than headline features. A few changes will be visible once they land on a stable release: the Mutter window compositor now supports a background blur effect on Wayland, GNOME Shell can honor a system-wide “reduced motion” setting for people sensitive to animations, and GNOME now offers SVG-based cursor themes in the same format KDE uses, meaning cursor themes should work across both desktops. The Settings app gained a new interface for managing fingerprints under the Users section, and GNOME Initial Setup, the wizard that runs on first login now supports systemd-homed accounts, a newer way of managing user home directories.
Under the hood, GTK reworked its frame-timing code to cut down on dropped frames, GNOME Software sped up icon loading, and the GVFS file-system layer added auto-unmounting for idle network and device connections. GNOME Web (Epiphany) re-enabled WebRTC support, restoring in-browser video calling, and the Glycin image-loading library picked up support for the Radiance HDR image format. One notable absence: the long-planned GTK4 rewrites of GNOME Boxes and GNOME Disks didn’t make it into this release after all, despite earlier signals they might.
Trying it out
For anyone curious, a live ISO is available to boot without installing on real hardware or in a virtual machine with EFI support, such as GNOME Boxes. It’s explicitly beta-quality software, so it’s not meant for a daily-driver install. The release candidate is expected around the end of August, with GNOME 51.0 stable slated for September 12. Most users are better off waiting for that stable release, which should arrive through their distribution’s normal update channels.
