Proof Portal

Sign in
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-5000GitHub issuePublicReceived

Super+J sends unsupported togglesplit message in scrolling layout

Reported by theontho · filed Sep 10, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7556 (R-1641). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Super+J sends unsupported togglesplit message in scrolling layoutrevision 1 · captured 2026-10-04 12:10 UTC via poll

System details

AMD Ryzen 5 5600X, NVIDIA GeForce RTX 3090, Omarchy 4.0.3-1, Hyprland 0.56.2

What's wrong?

Super+J produces the following Hyprland error when the active workspace is using the scrolling layout:

=[C]:-1: no such layoutmsg for scrolling

Steps to reproduce

  1. Press Super+L to change the active workspace from dwindle to scrolling.
  2. Confirm hyprctl activeworkspace -j | jq -r .tiledLayout prints scrolling.
  3. Press Super+J.
  4. Check hyprctl configerrors and observe no such layoutmsg for scrolling.

The stock bindings expose both actions:

o.bind("SUPER + J", "Toggle window split", hl.dsp.layout("togglesplit"))
o.bind("SUPER + L", "Toggle workspace layout", "omarchy-hyprland-workspace-layout-toggle")

omarchy-hyprland-workspace-layout-toggle intentionally switches the current workspace between dwindle and scrolling, but togglesplit is only supported by the dwindle layout.

Expected behavior

Super+J should not dispatch togglesplit while the active workspace uses scrolling. It could either be a no-op with a useful notification, or use a layout-aware action. A local workaround is to check .tiledLayout before dispatching the layout message.

View raw text
### System details

AMD Ryzen 5 5600X, NVIDIA GeForce RTX 3090, Omarchy 4.0.3-1, Hyprland 0.56.2

### What's wrong?

`Super+J` produces the following Hyprland error when the active workspace is using the scrolling layout:

```text
=[C]:-1: no such layoutmsg for scrolling
```

#### Steps to reproduce

1. Press `Super+L` to change the active workspace from `dwindle` to `scrolling`.
2. Confirm `hyprctl activeworkspace -j | jq -r .tiledLayout` prints `scrolling`.
3. Press `Super+J`.
4. Check `hyprctl configerrors` and observe `no such layoutmsg for scrolling`.

The stock bindings expose both actions:

```lua
o.bind("SUPER + J", "Toggle window split", hl.dsp.layout("togglesplit"))
o.bind("SUPER + L", "Toggle workspace layout", "omarchy-hyprland-workspace-layout-toggle")
```

`omarchy-hyprland-workspace-layout-toggle` intentionally switches the current workspace between `dwindle` and `scrolling`, but `togglesplit` is only supported by the dwindle layout.

#### Expected behavior

`Super+J` should not dispatch `togglesplit` while the active workspace uses scrolling. It could either be a no-op with a useful notification, or use a layout-aware action. A local workaround is to check `.tiledLayout` before dispatching the layout message.

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.