Mango Wayland Compositor 0.17.1 ships as a "bug fix" that quietly bundles new features
Mango's maintainer calls its latest patch a corrective bump, but it actually carried 15 commits of new functionality past the 0.17.0 milestone.
The 0.17.0 milestone tag was cut on September 12, 2026. Three days later, DreamMaoMao tagged 15 more commits as 0.17.1. But here's the quirk that makes this one worth a closer look: the version string in meson.build stayed pinned at 0.17.0 through 14 of those commits. It only flipped to 0.17.1 in the final bump. So anyone who built from main between the two tags was actually running 0.17.1 code while reporting "mango 0.17.0" as their version. Bug reports from the time confirm the drift. Issues citing commits e2b9ca85 and fb36fb46 labeled themselves 0.17.0 even though both landed in 0.17.1. For what it's worth, that's a textbook case of a git tag and the reported version string drifting apart.
Inside the 15 commits
Beyond the fixes, the new commits brought a handful of things worth naming. Virtual monitors can now be given a name at creation time, and there's a global idleinhibit_when_fullscreen option that stops the compositor from managing idle state while a window goes fullscreen.
The most structural change is a new systemd session target, mango-session.target. It pulls in graphical-session.target at startup, which lets portals and panels come up cleanly. xdg-desktop-portal 1.22 or newer refuses to start unless that target is active, and it's a RefuseManualStart, so it has to be pulled in via BindsTo. If you've ever had your panels spawn late or your portals misbehave, this is the fix.
For people who juggle multiple displays, focusmon and tagmon gained prev and next commands. They cycle forward and backward between monitors instead of jumping to an absolute index. Small thing. But it's the kind of keybind you end up using all day.
Then there's the stuff aimed at gamers. One fix addresses fullscreen games that render their swapchain twice as large as they should when the X11 primary output is unset or sitting on a different monitor. That's a genuinely annoying bug. The other, named explicitly in the note, follows a pointer-constraint cursor hint. When a locked-pointer client commits a new cursor position, the compositor now warps its own cursor to match. This is the core of the "wine games cursor capture" improvement, and it's the reason the note bothered to mention gaming at all.
Here's the honest read: MangoWM is clearly pushing gaming as a real priority rather than a marketing afterthought. Both fixes are day-to-day pain points, not gimmicks. That lines up neatly with the project's stated "practicality over novelty" ethos.
There's a catch, though. This build rides the newest wlroots line. It requires wlroots-0.20, libinput at or above 1.27.1, wayland-server 1.23.1 or newer, and scenefx-0.5. Chasing the bleeding-edge wlroots carries its own stability risk, and the project's own open PRs to keep the wl-only branch building against wlroots 0.20 make clear it's still a moving target. And there are no prebuilt binaries, so you either compile from source (usually yay -S mangowm-git on Arch) or accept a distro package that tends to lag behind main.
What MangoWM is and where it's going
To put 0.17.1 in perspective, remember what 0.17.0 already shipped. That milestone, released September 12, came with breaking changes, including the drop of tablet_map_to_mon and touch_map_to_mon in favor of per-device devicerule binding. It also added special floating workspaces, dwindle-layout focus memory, scratchpad animations, smooth follow gestures, one-time window rules, and an overview hotarea toggle. So 0.17.1 is corrective work layered on top of a fairly feature-rich foundation, which is probably why it stayed lean.
The project still bills itself as "dwm but wayland," and it leans into that identity. It keeps dwl's lightweight philosophy but adds tags instead of workspaces, animations, flexible layouts like scroller and dwindle, window effects like blur and corner radius, a Sway-like scratchpad, and hot-reload config. As of the research date it sits at 3.6k stars, 239 forks, 146 open issues, and 65 open PRs across 2,083 commits.
The roadmap hints at where the maintainer's head is at. Notable open PRs include HDR support via a color-management protocol with automated EDID luminance parsing, border textures and gradients, per-keyboard input layouts, and a config-parse bug fix. HDR would be the headline item, since it opens the door to native Proton and Wine HDR for DX11, DX12, and Vulkan.
If you want to try 0.17.1 yourself, the Arch AUR package is mangowm-git, which pulls a rolling git build straight from main. Fedora, Gentoo, Guix, NixOS, openSUSE, PikaOS, and AerynOS have packages too, though they often trail the source builds. Full docs and the keybinding reference live at mangowm.github.io, with the community on Discord. Keep in mind that this is a source-only release, so expect to build it yourself unless your distro already packaged it.
Head here for the GitHub release page.
