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

Problem starting a screen recording (region or display)

Reported by richecr · filed Oct 17, 2025Closed upstream on 2025-10-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 starting a screen recording (region or display)revision 1 · captured 2026-10-04 11:42 UTC via poll

System details

AMD Ryzen 5 5600X, NVIDIA GeForce RTX 3060 Ti GDDR6X, 2560x1440 in 32", 165 Hz, Omarchy v3.0.2, Linux 6.17.1-arch1-1, Hyprland 0.51.1 (Wayland)

What's wrong?

When I try to start a recording — either for a specific region or the entire display, with or without audio — it appears to start normally. However, once it finishes, no file shows up in the video folder.

When running the command:

omarchy-cmd-screenrecord

It shows the following error::

~                                                                                                      01:16:26
❯ omarchy-cmd-screenrecord

~                                                                                                      01:17:10
❯ selected region 57,182 1190x1048
Setting codec option: crf=23
Setting codec option: movflags=+faststart
Setting codec option: preset=medium
Setting codec option: tune=zerolatency
[Sink @ 0x7f1a50005880] Option 'pix_fmts' is not a runtime option and so cannot be set after the object has been initialized
Failed to set pix_fmts: Invalid argument

Can anyone help me understand the reason for this error?

View raw text
### System details

AMD Ryzen 5 5600X, NVIDIA GeForce RTX 3060 Ti GDDR6X, 2560x1440 in 32", 165 Hz, Omarchy v3.0.2, Linux 6.17.1-arch1-1, Hyprland 0.51.1 (Wayland)

### What's wrong?

When I try to start a recording — either for a specific region or the entire display, with or without audio — it appears to start normally. However, once it finishes, no file shows up in the video folder.

When running the command:
```sh
omarchy-cmd-screenrecord
```

It shows the following error::
```sh
~                                                                                                      01:16:26
❯ omarchy-cmd-screenrecord

~                                                                                                      01:17:10
❯ selected region 57,182 1190x1048
Setting codec option: crf=23
Setting codec option: movflags=+faststart
Setting codec option: preset=medium
Setting codec option: tune=zerolatency
[Sink @ 0x7f1a50005880] Option 'pix_fmts' is not a runtime option and so cannot be set after the object has been initialized
Failed to set pix_fmts: Invalid argument
```

Can anyone help me understand the reason for this error?

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.