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-4685GitHub issuePublicReceived

Super+J (togglesplit) errors on scrolling layout: 'no such layoutmsg for scrolling'

Reported by khru · filed Aug 25, 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 (togglesplit) errors on scrolling layout: 'no such layoutmsg for scrolling'revision 1 · captured 2026-10-04 12:03 UTC via poll

Description

When a workspace is set to the scrolling layout (via Super+L), pressing Super+J throws a runtime error:

Runtime error in lua: ?.? no such layoutmsg for scrolling

The Super+J binding calls hl.dsp.layout("togglesplit"), which is a layout message that only exists in the dwindle layout. The scrolling layout does not handle this message.

Steps to reproduce

  1. Press Super+L to toggle the workspace layout to scrolling
  2. Press Super+J
  3. Error appears

Expected behavior

Either:
- The togglesplit binding is a no-op on non-dwindle layouts (no error), or
- The binding is conditional and only works on dwindle workspaces

Workaround

Delete the workspace layout file:

rm ~/.local/state/omarchy/workspace-layouts/<workspace-id>.lua

Or toggle back to dwindle with Super+L.

System details

  • Omarchy version: 4.0.1-1
  • Layout: scrolling (workspace-specific)
  • Default binding in /usr/share/omarchy/default/hypr/bindings/tiling.lua line 4:
  o.bind("SUPER + J", "Toggle window split", hl.dsp.layout("togglesplit"))

Suggested fix

The binding could check the current workspace layout before dispatching togglesplit, or the error could be silently ignored for unsupported layouts.

View raw text
## Description

When a workspace is set to the `scrolling` layout (via `Super+L`), pressing `Super+J` throws a runtime error:

```
Runtime error in lua: ?.? no such layoutmsg for scrolling
```

The `Super+J` binding calls `hl.dsp.layout("togglesplit")`, which is a layout message that only exists in the `dwindle` layout. The `scrolling` layout does not handle this message.

## Steps to reproduce

1. Press `Super+L` to toggle the workspace layout to `scrolling`
2. Press `Super+J`
3. Error appears

## Expected behavior

Either:
- The `togglesplit` binding is a no-op on non-dwindle layouts (no error), or
- The binding is conditional and only works on dwindle workspaces

## Workaround

Delete the workspace layout file:
```bash
rm ~/.local/state/omarchy/workspace-layouts/<workspace-id>.lua
```

Or toggle back to dwindle with `Super+L`.

## System details

- Omarchy version: 4.0.1-1
- Layout: scrolling (workspace-specific)
- Default binding in `/usr/share/omarchy/default/hypr/bindings/tiling.lua` line 4:
  ```lua
  o.bind("SUPER + J", "Toggle window split", hl.dsp.layout("togglesplit"))
  ```

## Suggested fix

The binding could check the current workspace layout before dispatching `togglesplit`, or the error could be silently ignored for unsupported layouts.

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.