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

Problem with binds after 3.4.2 update

Reported by RodrigoAroeira · filed Mar 9, 2026Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

Problem with binds after 3.4.2 updaterevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

i7-8650U, Omarchy 3.4.2

What's wrong?

After updating to v3.4.2, I noticed that some bind combinations weren't working as before

Issue 1 - Modifier order matters

Some modifier combinations only work if the modifiers are pressed in a specific order.

Example

SUPER SHIFT ALT + <key>

Now only works if you press ALT before the SHIFT`, effectively requiring:

SUPER ALT SHIFT + <key>

If SHIFT is pressed before ALT, either nothing happens or <key> is registered as normal input instead of triggering the bind

Issue 2 - Workspace switching after moving a window

After moving a window with:

SUPER SHIFT + {number}

I can't directly switch to a workspace with

SUPER + {number}

until I release SUPER and then press it again first.

Expected behavior

Both combinations should work regardless of the order the modifiers are pressed and workspace switching should work immediately after moving a window without releasing SUPER, like in the 3.4.1 update and before.

Additional info

I talked with others in the official Omarchy discord server, who reported the same behavior is happening to them.

omarchy-debug output

omarchy-debug.log

View raw text
### System details

i7-8650U, Omarchy 3.4.2

### What's wrong?

After updating to v3.4.2, I noticed that some bind combinations weren't working as before

## Issue 1 - Modifier order matters
Some modifier combinations only work if the modifiers are pressed in a specific order.

### Example
 `SUPER SHIFT ALT + <key>`

Now only works if you press ALT before the SHIFT`, effectively requiring:

`SUPER ALT SHIFT + <key>`

If `SHIFT` is pressed before `ALT`, either nothing happens or <key> is registered as normal input instead of triggering the bind

## Issue 2 - Workspace switching after moving a window
After moving a window with:

`SUPER SHIFT + {number}`

I can't directly switch to a workspace with

 `SUPER + {number}` 

until I release `SUPER` and then press it again first.

## Expected behavior
Both combinations should work regardless of the order the modifiers are pressed and workspace switching should work immediately after moving a window without releasing `SUPER`, like in the 3.4.1 update and before.

## Additional info

I talked with others in the official Omarchy discord server, who reported the same behavior is happening to them.

## omarchy-debug output

[omarchy-debug.log](https://github.com/user-attachments/files/25843473/omarchy-debug.log)
  • omarchy-debug.log

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.