Hyprland 0.57 drops .conf configs, and a titlebars plugin pin stalled Omarchy’s edge updates
Omarchy’s Lua config sails through the end of .conf support. The snag was a titlebars plugin pinned to Hyprland 0.56.2, which made omarchy update abort on edge.
Image: Hyprland 0.57 release notes (hypr.land)
Hyprland 0.57.0 is out, and it comes with a big break: “starting with this version, .conf configs are no longer supported.” For Omarchy, that headline is a non-event. Omarchy 4 already ships its Hyprland config as Lua, with hyprland.lua, bindings.lua, input.lua, looknfeel.lua and friends in the repo’s config/hypr folder and no hyprland.conf in sight. The part of 0.57 that does bite is a packaging problem, and every report so far comes from the edge channel.
First, the good stuff. According to the 0.57 release notes, published on October 28, 2026, you can now screenshare a whole workspace, in both Hyprland and XDPH. There’s a window wobble effect (“If you are still yearning for the good old days of compiz, I have something for you”), many more blur options, plus a proportional one, new no_glow and no_wobble rules and a new cursor:warp_on_monitor_change option. The Lua API grows too, with a config.unload event, hl.reload_config(), hl.get_devices() and new window minimize and state update events. “Hyprland 0.57.0 is finally here, with tons of new stuff you don’t wanna miss!” the Hyprland account posted on X.
Now the snag. In an issue opened late on October 28, 2026, @loraque-git reports that omarchy update on edge x86_64 dies at “Update system packages” with installing hyprland (0.57.0-1) breaks dependency 'hyprland=0.56.2' required by omarchy-hyprland-titlebars. Nothing gets upgraded and the desktop stays on Hyprland 0.56.2-4. The culprit is omarchy-hyprland-titlebars 0.2.2-2, which depends on exactly hyprland=0.56.2, the version it was compiled against. The reporter notes that the plugin is in Omarchy’s base package list, so this is the stock update path, not some optional extra.
Three more users have confirmed it in the thread, all on the edge channel, with the same versions installed and the same abort. @shawnyeager found the way out: removing omarchy-hyprland-titlebars let the update finish, and his machine is now on hyprland 0.57.0-1. The catch, in his words: the edge repo still serves 0.2.2-2 with its 0.56.2 pin, “so the plugin cannot be installed again until a rebuild is published.” So if you take that route, you go without the titlebars plugin until a rebuilt package lands.
Omarchy’s packaging is supposed to catch exactly this. The titlebars package is set to rebuild whenever Hyprland moves, and an automated pull request, omarchy-pkgs #1788, opened early on October 29, 2026 to bump it to 0.2.2-3. It “auto-merges once the build checks pass,” and that’s where it gets stuck: according to the fix PR below, that rebuild fails on x86_64 because the plugin no longer compiles against 0.57, starting with Window.hpp: No such file or directory.
The actual fix is “Build against Hyprland 0.57” from @felipecpaiva in the titlebars repo. It ports the plugin “the way hyprwm/hyprland-plugins did hyprbars for 0.57”: title drags and top-edge resizing now go through the layout manager’s drag targets, button commands spawn through the executor, and the old hyprlang keyword handler is gone. “0.57 has no legacy config, so only hl.plugin.hyprbars.add_button remains” for defining buttons. The PR says it compiles and links against the 0.57.0-1 headers with no new warnings, but it is honest about the gap: it was “Not run against a live 0.57 compositor,” and the touch drag and top-edge resize paths “are the ones to watch.”
So when does Omarchy edge get Hyprland 0.57 without workarounds? The PR spells out the path: “After merging, a new tag lets omarchy-pkgs bump the package.” That means merge #7, tag a new titlebars release, rebuild, and omarchy update goes through again. As of the morning of October 29, 2026, the issue is open, neither PR has been merged, and the latest titlebars tag is v0.2.2. None of the threads gives a date.
Until then, edge users have two choices: wait for the rebuilt plugin, or remove omarchy-hyprland-titlebars, update to 0.57 and reinstall the plugin once the new build is out. Either way, the move to Lua that Omarchy made in version 4 is paying off: the end of .conf support doesn’t touch the config of a stock install.
