MangoWC 0.17.2 ships a stability patch for the dwl-derived Wayland compositor
A tiny, single-purpose release from the "dwm but Wayland" project.
MangoWC 0.17.2 is now available and it knows exactly what it was built for. The maintainer's description is one sentence: "Fix some crash and build issues, as well as potential memory leaks." No features. No demo reel. No breaking changes, which, after the past week, is a relief.
The 0.17 streak, in order
You need context for why 0.17.2 reads like pure housekeeping. The milestone release, 0.17.0, dropped on September 12 and pulled in roughly 80 reactions. DreamMaoMao called it the point where "all originally planned features have been fully implemented," while also reorganizing the codebase into a "standard LSP-friendly C project structure." That version shipped two breaking changes alongside the flashier additions.
Its changelog is long. You get a special floating workspace, enhancements to the Dindle layout, scratchpad animations, no-modifier-key dragging, a windowrule-once rule, and a confine_pointer option to trap your cursor inside a game window. It also dropped tablet_map_to_mon and touch_map_to_mon in favor of per-output device rules. That is a lot of machinery to drop on people at once.
Then 0.17.1 landed on September 15 with 22 reactions, mostly cleaning up the minor regressions 0.17.0 had left behind and improving cursor capture for Wine games. 0.17.2 is the third leg, and it targets the bugs that only surface once real users start piling work onto the thing.
What the code actually says
The notes are thin, so the real scope has to be read off the commit history. Four commits have landed on main since the 0.17.2 tag, and they point straight at the areas this cycle was trying to patch.
One stands out. Commit 51fab2a, dated September 18, fixes "a wild pointer after configuration reloading." That is a dangling pointer that appears when you hot-reload your config, and it ties directly to the crash and memory-leak promises in the release notes. Not the class of bug you want to write a press release about, but a dangling pointer is a dangling pointer.
The other three cluster around tag animations and build plumbing. c008627 keeps tag animation state for clients not sitting in their slot. cc25daa simplifies the tag animation code path. And 42cdf41 drops a SOCK_CLOEXEC flag, which is likely the cause of the build issues the maintainer mentioned.
Taken together, the terse description maps cleanly onto real problems. Tag animations, config hot-reload memory safety, socket plumbing. That is basically the entire ballgame for 0.17.2.
MangoWC sits in a crowded corner of the Wayland world, where dwl-derived compositors are a dime a dozen but a well-maintained one is far rarer than the star count suggests. This week is really just one maintainer taking a large feature milestone from "implemented" to "stable" as fast as hardware and sleep allow. Feature grabs the headlines. A compositor that stops dying when you reload your config is what keeps people using it on a regular Tuesday.
That said, the patch was genuinely small. If you were holding out for 0.17.2 to ship something new, keep in mind that this is not the release to do it in.
On Arch, grab the git package with yay -S mangowm-git. Fedora, Gentoo, Guix, NixOS, openSUSE, PikaOS, and AerynOS all have setup notes on the project site. Building from source uses Meson, and a Nix flake is there if that is your preference. Docs live at mangowm.github.io, and there is a community Wiki plus a Discord server for when the config file inevitably fights back.
The repo sits at github.com/mangowm/mango under GPL-3.0, resting at roughly 3,600 stars and 242 forks, with 150 open issues and 67 pull requests still in the queue as of September 18. Upgrading to 0.17.2 is the recommended step before you adopt any of the post-0.17.2 commits already rolling toward the next tag.
Head here to the release page if you want to eyeball the SHAs and commit diffs yourself.
