OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
hyprland-config low occasional DISPUTE

Get your configured master layout back after SUPER+L pinned a workspace to dwindle

omarchyhyprland
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

The cause and fix hold. /usr/share/omarchy/bin/omarchy-hyprland-workspace-layout-toggle on 4.0.4-1 is byte-identical to quattro. It maps dwindle to scrolling and everything else to dwindle, and writes hl.workspace_rule to ~/.local/state/omarchy/workspace-layouts/<id>.lua. workspace-layouts.lua loads that directory on every config load through require_all. Issue #7612 (open) reports exactly this. The verify step is wrong. In Hyprland v0.56.2, HyprCtl.cpp's workspacerules JSON never emits a layout field. It only emits workspaceString, enabled, monitor, gaps and similar fields. So select(.layout != null) always prints nothing, even when stale rules exist. This workstation shows it: state files 1.lua and 2.lua exist, and hyprctl workspacerules -j lists workspaces 1 and 2 with no layout key. The verify was rewritten. Deleting state files and reloading were not exercised here.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

You set general = { layout = "master" } in ~/.config/hypr/looknfeel.lua, but some workspaces always come back as dwindle or scrolling after a reload or reboot. Pressing SUPER+L only flips between dwindle and scrolling and never returns to master. Restoring your ~/.config/hypr backup changes nothing.

Cause

omarchy-hyprland-workspace-layout-toggle (SUPER+L) writes hl.workspace_rule({ workspace = "<id>", layout = "<dwindle|scrolling>" }) to ~/.local/state/omarchy/workspace-layouts/<id>.lua, and /usr/share/omarchy/default/hypr/workspace-layouts.lua loads every file in that directory on each config load. A workspace rule outranks general.layout, so one press pins that workspace for good. The script maps dwindle to scrolling and everything else to dwindle, so master can never be reached again through it. The state lives outside ~/.config/hypr, which is why a config restore does not help. Confirmed in the 4.0.4-1 script and on quattro.

Fix

**Omarchy 4.** Delete the saved per-workspace layouts, then reload:


ls ~/.local/state/omarchy/workspace-layouts/
rm -f -- ~/.local/state/omarchy/workspace-layouts/*.lua
hyprctl reload

If you never want SUPER+L to persist a layout, remove the bind in ~/.config/hypr/bindings.lua:


hl.unbind("SUPER + L")

To pin a workspace to a layout on purpose, write the rule yourself in ~/.config/hypr/hyprland.lua, where you can see it:


hl.workspace_rule({ workspace = "3", layout = "master" })

Workspaces that already exist keep the live rule until the reload, and a fresh login is the cleanest check.

Verify


ls ~/.local/state/omarchy/workspace-layouts/ 2>/dev/null
hyprctl workspacerules -j | jq -r '.[].workspaceString'
hyprctl activeworkspace -j | jq .tiledLayout

The directory is empty or missing. No workspaceString entry remains for the workspaces you had toggled, unless your own config defines one. Hyprland 0.56.2 does not print a rule's layout in this JSON, so a leftover entry is the only sign. The active workspace reports "master".

Sources

workspace-layout-toggle-overrides-global-layout