Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
SUPER + J errors on scrolling-layout workspaces
Reported by seth-wood · filed Aug 29, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7556 (R-1641). GitHub close reason: completed.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
AMD Ryzen 5 PRO 4650U, Radeon Vega (Renoir), Omarchy 4.0.1-1, Hyprland 0.56.2
What's wrong?
SUPER + J errors on any workspace using the scrolling layout:
error: =[C]:-1: no such layoutmsg for scrolling
Two stock bindings conflict. SUPER + L puts the active workspace into
Hyprland's scrolling layout, and SUPER + J dispatches a dwindle-only layout
message:
-- default/hypr/bindings/tiling.lua:4
o.bind("SUPER + J", "Toggle window split", hl.dsp.layout("togglesplit"))
Steps to reproduce, on stock config:
SUPER + Lto switch the active workspace to scrollingSUPER + J
Or without keybindings:
hyprctl dispatch 'hl.dsp.layout("togglesplit")'
Expected SUPER + J to no-op on a scrolling workspace instead of surfacing a
Hyprland error.
Hyprland doesn't intend to silence unsupported layout messages -- in
hyprwm/Hyprland discussion #14237 the suggested resolution is for the caller
to check the active layout first. So the guard likely belongs here, e.g. onhyprctl activeworkspace -j | jq -r .tiledLayout, which
omarchy-hyprland-workspace-layout-toggle already reads.
Happy to open a PR if the approach sounds right.
View raw text
### System details
AMD Ryzen 5 PRO 4650U, Radeon Vega (Renoir), Omarchy 4.0.1-1, Hyprland 0.56.2
### What's wrong?
`SUPER + J` errors on any workspace using the scrolling layout:
error: =[C]:-1: no such layoutmsg for scrolling
Two stock bindings conflict. `SUPER + L` puts the active workspace into
Hyprland's scrolling layout, and `SUPER + J` dispatches a dwindle-only layout
message:
-- default/hypr/bindings/tiling.lua:4
o.bind("SUPER + J", "Toggle window split", hl.dsp.layout("togglesplit"))
Steps to reproduce, on stock config:
1. `SUPER + L` to switch the active workspace to scrolling
2. `SUPER + J`
Or without keybindings:
hyprctl dispatch 'hl.dsp.layout("togglesplit")'
Expected `SUPER + J` to no-op on a scrolling workspace instead of surfacing a
Hyprland error.
Hyprland doesn't intend to silence unsupported layout messages -- in
hyprwm/Hyprland discussion #14237 the suggested resolution is for the caller
to check the active layout first. So the guard likely belongs here, e.g. on
`hyprctl activeworkspace -j | jq -r .tiledLayout`, which
omarchy-hyprland-workspace-layout-toggle already reads.
Happy to open a PR if the approach sounds right.
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.
No decision has been recorded yet.