If you are on Budgie, you have probably noticed a particular kind of friction that nobody talks about in feature lists. You drag a file to the desktop, you let go, and it lands on a gridline that does not actually look like a gridline until you pay attention. Then you try to nudge it two pixels to the left, and it jumps to the next slot. The desktop is technically a free surface, but it never really feels free. The September 27, 2026 update to Budgie (10.10.3) is the first release in a while that actually fixes it, and the fix is more interesting than the headline lets on.
Six months of work landed in a maintenance release rather than a feature release, which is a deliberate choice by the Buddies of Budgie team. Maintenance releases are usually where you ship the bug fixes you have been too embarrassed to mention in the changelog, and 10.10.3 has enough of those that it deserves more attention than it is getting.
The icon snapping change is more invasive than it sounds
Free placement means the desktop icon grid is gone. Not “off by default” gone, but actually gone. You can drop an icon into the corner of a 4K monitor and it stays there. You can stack three icons in the same spot and they live as a pile. You can run a multi-display setup where the primary monitor is on the right and the icons on the secondary monitor do not auto-snap to its top-left grid. None of this is technically complex. The interesting part is that Budgie has been carrying an icon-grid implementation since the 10.x series started, and ripping it out cleanly without breaking the rest of the desktop layout took a lot of careful work.
The catch is that the team did not ship an undo for icon position. If you are someone who rearranges your desktop weekly, take a screenshot first. The grid was annoying, but it was also predictable. The free placement will feel slightly chaotic for the first few days until your muscle memory rewires.
What changed under the hood (and why it took six months)
The Polkit authorization dialog (the prompt that appears when an app asks for elevated privileges, like installing a package or restarting a service) had a high-CPU hang that would also block shutdown, logout, and restart commands from responding. If you have ever tried to shut down a Budgie session and watched the system sit there for thirty to ninety seconds doing nothing, that hang was likely your culprit. The fix is a rewrite of the dialog’s response handler so the CPU spike cannot wedge the whole session in a busy-wait loop. The same fix resolved a related symptom where Do Not Disturb state would drift out of sync between Raven (the slide-out settings and notifications panel) and the system tray applet.
- Polkit dialog no longer pegs a CPU core during authorization.
- Logout, restart, and shutdown dialogs respond immediately, even during a Polkit session.
- Do Not Disturb state stays consistent across Raven and the system tray.
- Tasklist jitter on narrow panels (under 40 pixels) is gone.
- Workspace plus and minus buttons increment by one instead of jumping to extremes.
- Electron apps like Proton Mail and Proton Pass group correctly in the Icon Tasklist.
- Wine-spawned apps (Lutris-launched games in particular) no longer crash the System Tray on launch.
- Wallpaper now syncs correctly with the login screen on logout.
- Minimize keyboard action works again for Firefox and other GTK apps that broke it in 10.10.2.
These are the kind of fixes you only notice once they ship, which is the highest compliment you can give a maintenance release.
Two features that quietly returned after years away
The Keyboard Layout applet and the primary-monitor selector are both back in Raven. These are not flashy features, but their absence had been a thorn for anyone running a multilingual setup or a multi-monitor desk. The Keyboard Layout applet was dropped in a 10.x refactor a couple of years back, and the workaround was either to bind keyboard shortcuts manually or to install a third-party panel plugin that did the same job less reliably. Its return is a quiet admission that the refactor was the wrong call.
The primary-monitor selector matters more than it sounds if you run two or three displays. Without it, Budgie insisted on routing panels, notifications, and fullscreen apps to the first detected monitor every reboot, regardless of which screen was actually primary. With it back, you can mark a monitor as primary once, and that choice survives reboots and reconnects.
- Keyboard Layout applet is back on the panel.
- Primary monitor can be picked explicitly in Raven and the setting persists.
- Multimedia keys (volume, brightness, play/pause) work out of the box without manual keybinding.
- Launcher hotkeys are wired up for terminal, calculator, browser, file manager, and media player.
Raven stretches and the usage monitor starts telling the truth
Raven used to stop short of the top and bottom edges of the screen, which left a thin strip of empty wallpaper above and below the panel when Raven was open. Most people never noticed, and the ones who did eventually stopped noticing. Now Raven stretches edge to edge, which is the kind of detail that makes a desktop feel like it was designed instead of patched together.
The Usage Monitor widget switched its backend from an old custom implementation to libgtop, which is the library most other GNOME-based desktops use to read live CPU, memory, and network stats. The custom implementation had been showing stale numbers for months, and switching to libgtop means the values update properly during heavy load. If you have ever glanced at the Usage Monitor and ignored it because it was showing last Tuesday’s numbers, this fix is for you.
Wayland, Labwc, and what the spec support means
Wayland remains the only session type in the 10.10 series, which is worth saying again because the question comes up regularly on the Budgie forum. If you depend on an X11-only driver or application, this release is not going to bring it back. The Labwc bridge (the connector between Budgie’s session daemon and the Labwc Wayland compositor) now listens to budgie-daemon for session status updates that used to go missing in some Labwc session configurations. That fix is mostly invisible unless you were specifically hitting it, but the under-the-hood integration work means fewer session-state weirdnesses in mixed setups.
Freedesktop.org thumbnail spec support also landed, which is the kind of fix that makes Budgie match what KDE, GNOME, and XFCE have been doing for years. If your file manager follows the spec, it will now generate previews for image, video, and document files using a consistent standard, and previews will survive thumbnail cache resets instead of regenerating from scratch.
Trade-offs
The free placement change ships without an undo, which is the obvious trade-off. If you rearrange often, screenshot first. The maintenance fixes only matter if you actually update, and distro packaging will dictate how fast 10.10.3 reaches your package manager. None of the smaller features (Keyboard Layout applet, primary monitor selector, multimedia keys) tip the scale on their own if you are evaluating Budgie for the first time, but together they make Budgie the most polished release of the 10.10 series.
The Wayland-only commitment is a hard line, not a soft one. If you have an X11-only driver that is not getting updated, this is not the release that solves that. The Raven stretch and the Usage Monitor fix are the kind of polish that compounds over months, not the kind that wins comparison reviews on day one. The oo7 Secret Service provider (the back end that handles password and token storage for sandboxed apps) is opt-in for GNOME Keyring users, and most people will never touch the setting, which is fine.
Migration cost is low. Existing Budgie users get the upgrade through their distro’s package manager in the usual way. If you have been on the fence about Budgie, this is the most polished release of the 10.10 series so far, and the Wayland-only commitment finally feels like a feature instead of a constraint. If you can run a Wayland session and you do not depend on X11-only apps, this is a clean fit.
Update as soon as your distro pushes 10.10.3. The Polkit fix alone justifies the reboot.