Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-778GitHub issuePublicDecided· Out of scope

Single-window square aspect toggle reports success but does nothing on scrolling-layout workspaces

Reported by haydenmckay · filed Sep 9, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Single-window square aspect toggle reports success but does nothing on scrolling-layout workspacesrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Lenovo 82TT, Intel i5-1235U / Iris Xe, single eDP-1 1920x1080 @ scale 1, Omarchy 4.0.3-1, Hyprland 0.56.2

What's wrong?

Summary

SUPER + CTRL + BACKSPACE ("Toggle single-window square aspect") fires its success notification and flips global state, but has no effect on any workspace using the scrolling layout. single_window_aspect_ratio is a dwindle option and the scrolling layout ignores it. Because SUPER + L sets the layout per workspace and persists it, the same keybind works on some workspaces and silently does nothing on others — with an identical "Enable single-window square aspect ratio" notification either way. There is no feedback anywhere that distinguishes the two cases.

Mechanism

  • omarchy-hyprland-window-single-square-aspect-toggle calls omarchy-hyprland-toggle single-window-aspect-ratio, which copies default/hypr/toggles/single-window-aspect-ratio.lua into ~/.local/state/omarchy/toggles/hypr/ and reloads. That file sets layout.single_window_aspect_ratio = { 1, 1 } — a global option.
  • omarchy-hyprland-workspace-layout-toggle (SUPER + L) writes hl.workspace_rule({ workspace = "<id>", layout = "scrolling" }) to ~/.local/state/omarchy/workspace-layouts/<id>.lua, reapplied on every config load by default/hypr/workspace-layouts.lua.
  • The scrolling layout does not implement single_window_aspect_ratio, so a global flag silently applies to a per-workspace subset.

Steps to reproduce

  1. SUPER + CTRL + BACKSPACE → notification "Enable single-window square aspect ratio".
  2. On a dwindle workspace, open one tiled window → square. Correct.
  3. On another workspace press SUPER + L (→ scrolling), open one tiled window → full width.
  4. Press SUPER + CTRL + BACKSPACE twice more on that workspace. Both notifications fire. Geometry never changes.

Measured

Flag on, hyprctl getoption layout:single_window_aspect_ratio → vec2: [1, 1] / set: true. Same foot window, same monitor, moved between workspaces:

WorkspacetiledLayoutGeometry
3dwindle[445, 38] 1030x1030 ✅
4scrolling[12, 38] 1896x1030 ❌
8dwindle[445, 38] 1030x1030 ✅

Not the floating or fullscreen bypass: floating: false, fullscreen: 0 in all three. A floating companion window on the same workspace does not break it on dwindle either — layout is the only variable.

The user-visible symptom is that the feature looks broken and intermittent. Nothing in the UI surfaces a workspace's layout, so there's no way to connect "square aspect stopped working" to a SUPER + L press from weeks earlier.

Suggested fix

Same shape as #9988 for the other dwindle-only binds — gate on the active workspace's layout:

hl.get_active_workspace().tiled_layout == "dwindle"

At minimum, don't report "Enable single-window square aspect ratio" on a scrolling workspace. Better would be to say the flag has no effect there, since the flag is global while the layout is per-workspace — suppressing the notification alone would leave the keybind looking dead.

Related

  • #9988 / #9726 / #8220 / #9146 / #7556 — dwindle-only binds on scrolling workspaces. Those raise a visible no such layoutmsg for scrolling; this one is silent and reports success.
  • #7612 — the persisted per-workspace layout rule this interacts with.
View raw text
### System details

Lenovo 82TT, Intel i5-1235U / Iris Xe, single eDP-1 1920x1080 @ scale 1, Omarchy 4.0.3-1, Hyprland 0.56.2

### What's wrong?

**Summary**

`SUPER + CTRL + BACKSPACE` ("Toggle single-window square aspect") fires its success notification and flips global state, but has no effect on any workspace using the scrolling layout. `single_window_aspect_ratio` is a dwindle option and the scrolling layout ignores it. Because `SUPER + L` sets the layout **per workspace** and persists it, the same keybind works on some workspaces and silently does nothing on others — with an identical "Enable single-window square aspect ratio" notification either way. There is no feedback anywhere that distinguishes the two cases.

**Mechanism**

- `omarchy-hyprland-window-single-square-aspect-toggle` calls `omarchy-hyprland-toggle single-window-aspect-ratio`, which copies `default/hypr/toggles/single-window-aspect-ratio.lua` into `~/.local/state/omarchy/toggles/hypr/` and reloads. That file sets `layout.single_window_aspect_ratio = { 1, 1 }` — a **global** option.
- `omarchy-hyprland-workspace-layout-toggle` (`SUPER + L`) writes `hl.workspace_rule({ workspace = "<id>", layout = "scrolling" })` to `~/.local/state/omarchy/workspace-layouts/<id>.lua`, reapplied on every config load by `default/hypr/workspace-layouts.lua`.
- The scrolling layout does not implement `single_window_aspect_ratio`, so a global flag silently applies to a per-workspace subset.

**Steps to reproduce**

1. `SUPER + CTRL + BACKSPACE` → notification "Enable single-window square aspect ratio".
2. On a dwindle workspace, open one tiled window → square. Correct.
3. On another workspace press `SUPER + L` (→ scrolling), open one tiled window → full width.
4. Press `SUPER + CTRL + BACKSPACE` twice more on that workspace. Both notifications fire. Geometry never changes.

**Measured**

Flag on, `hyprctl getoption layout:single_window_aspect_ratio` → `vec2: [1, 1]` / `set: true`. Same `foot` window, same monitor, moved between workspaces:

| Workspace | `tiledLayout` | Geometry |
|---|---|---|
| 3 | dwindle | `[445, 38] 1030x1030` ✅ |
| 4 | scrolling | `[12, 38] 1896x1030` ❌ |
| 8 | dwindle | `[445, 38] 1030x1030` ✅ |

Not the floating or fullscreen bypass: `floating: false`, `fullscreen: 0` in all three. A floating companion window on the same workspace does not break it on dwindle either — layout is the only variable.

The user-visible symptom is that the feature looks broken and intermittent. Nothing in the UI surfaces a workspace's layout, so there's no way to connect "square aspect stopped working" to a `SUPER + L` press from weeks earlier.

**Suggested fix**

Same shape as #9988 for the other dwindle-only binds — gate on the active workspace's layout:

```lua
hl.get_active_workspace().tiled_layout == "dwindle"
```

At minimum, don't report "Enable single-window square aspect ratio" on a scrolling workspace. Better would be to say the flag has no effect there, since the flag is global while the layout is per-workspace — suppressing the notification alone would leave the keybind looking dead.

**Related**

- #9988 / #9726 / #8220 / #9146 / #7556 — dwindle-only binds on scrolling workspaces. Those raise a visible `no such layoutmsg for scrolling`; this one is silent and reports success.
- #7612 — the persisted per-workspace layout rule this interacts with.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 11:18 UTC