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

Print/SysReq key stopped working for screenshots after 3.7.1 update, found out it called wrong bindings.conf command

Reported by petipoua · filed May 7, 2026Closed upstream on 2026-05-08 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

Print/SysReq key stopped working for screenshots after 3.7.1 update, found out it called wrong bindings.conf commandrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Omarchy 3.7.1

What's wrong?

The problem

After updating Omarchy (early May 2026) to 3.7.1, Print key stopped working for triggering screenshots on my system.

I tracked it down to a command rename from omarchy-cmd-screenshot to omarchy-capture-screenshot (commit e76d7544), while my user override still referenced the old command. I didn't customize this key or command myself before. The migration script during the 3.7.1 update seems to have skipped this specific command update in my bindings.conf for some reason. Not sure why.

How to fix:

go to ~/.config/hypr/bindings.conf and replace:

bindd = , PRINT, Screenshot, exec, env OMARCHY_SCREENSHOT_DIR=/home/<user>/Pictures/screenshots omarchy-cmd-screenshot

with

`
bindd = , PRINT, Screenshot, exec, env OMARCHY_SCREENSHOT_DIR=/home/<user>/Pictures/screenshots omarchy-capture-screenshot`

View raw text
### System details

Omarchy 3.7.1

### What's wrong?

## The problem
After updating Omarchy (early May 2026) to 3.7.1, Print key stopped working for triggering screenshots on my system.

I tracked it down to a command rename from omarchy-cmd-screenshot to omarchy-capture-screenshot (commit e76d7544), while my user override still referenced the old command. I didn't customize this key or command myself before. The migration script during the 3.7.1 update seems to have skipped this specific command update in my bindings.conf for some reason. Not sure why.

## How to fix:

go to ~/.config/hypr/bindings.conf and replace:

`bindd = , PRINT, Screenshot, exec, env OMARCHY_SCREENSHOT_DIR=/home/<user>/Pictures/screenshots omarchy-cmd-screenshot`

with 

`
bindd = , PRINT, Screenshot, exec, env OMARCHY_SCREENSHOT_DIR=/home/<user>/Pictures/screenshots omarchy-capture-screenshot`

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.