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

Unable to screenrecord with audio

Reported by lukehsiao · filed Sep 17, 2025Closed upstream on 2025-09-18 by its own reporter lukehsiao. GitHub close reason: completed. Closed by its own reporter — not by itself 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

Unable to screenrecord with audiorevision 1 · captured 2026-10-04 11:35 UTC via poll

System details

AMD 7800X3D, RX 7800 XT, Omarchy v3.0.1

What's wrong?

~ at 17:20:43 ❯ RUST_BACKTRACE=1 omarchy-cmd-screenrecord region audio

~ at 17:20:54 ❯ [h264_vaapi @ 0x5636d06bf640] No usable encoding entrypoint found for profile VAProfileH264High (7).
failed to open encoder in low_power mode (Function not implemented), trying non low_power mode. if you have an intel iGPU, set enable_guc=2 in the i915 module to use the fixed function encoder. pass --low-power=off to suppress this warning

thread 'main' panicked at src/audio.rs:221:10:
called `Result::unwrap()` on an `Err` value: ffmpeg::Error(8: Exec format error)
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

If I run the screencrecord command with audio, it crashes when I stop the recording. Without audio seems to work fine.

My hypothesis is that wl-screenrec does not support AMD GPUs well, or we are missing some packages to use it.

Ref: https://github.com/russelltg/wl-screenrec/issues/132

View raw text
### System details

AMD 7800X3D, RX 7800 XT, Omarchy v3.0.1

### What's wrong?

```
~ at 17:20:43 ❯ RUST_BACKTRACE=1 omarchy-cmd-screenrecord region audio

~ at 17:20:54 ❯ [h264_vaapi @ 0x5636d06bf640] No usable encoding entrypoint found for profile VAProfileH264High (7).
failed to open encoder in low_power mode (Function not implemented), trying non low_power mode. if you have an intel iGPU, set enable_guc=2 in the i915 module to use the fixed function encoder. pass --low-power=off to suppress this warning

thread 'main' panicked at src/audio.rs:221:10:
called `Result::unwrap()` on an `Err` value: ffmpeg::Error(8: Exec format error)
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
```

If I run the screencrecord command with audio, it crashes when I stop the recording. Without audio seems to work fine.

My hypothesis is that `wl-screenrec` does not support AMD GPUs well, or we are missing some packages to use it.

Ref: https://github.com/russelltg/wl-screenrec/issues/132

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.