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-5273GitHub issuePublicDecided· Out of scope

Stable channel: gpu-screen-recorder 5.12.3-2 from [omarchy] is linked against ffmpeg 8, so screen recording fails with ffmpeg 9.0.1

Reported by ssandys · filed Oct 9, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Stable channel: gpu-screen-recorder 5.12.3-2 from [omarchy] is linked against ffmpeg 8, so screen recording fails with ffmpeg 9.0.1revision 1 · captured 2026-10-09 15:34 UTC via poll

System details

AMD Ryzen AI 9 HX 370 (Radeon 890M) + Radeon RX 9060 XT, Omarchy 4.0.4-1, stable channel

What's wrong?

On the stable channel, screen recording doesn't work. gpu-screen-recorder exits before it records anything, because it can't load its ffmpeg libraries:

$ gpu-screen-recorder -w DP-7 -s 0x0 -k auto -f 60 -fm cfr -fallback-cpu-encoding yes -o test.mp4
gpu-screen-recorder: error while loading shared libraries: libavcodec.so.62: cannot open shared object file: No such file or directory
$ ldd /usr/bin/gpu-screen-recorder | grep 'not found'
	libavcodec.so.62 => not found
	libavformat.so.62 => not found
	libavutil.so.60 => not found
	libswresample.so.6 => not found
	libavfilter.so.11 => not found

omarchy-capture-screenrecording fails for both region and fullscreen capture. Its gsr stderr goes to /dev/null unless OMARCHY_SCREENRECORD_DEBUG=true is set, so from the keybinding or menu the recording just never starts.

Cause: in the stable channel, two repos disagree.

Stable repogpu-screen-recorderffmpeg it was built against
[omarchy] (pkgs.omarchy.org/stable)5.12.3-28 (libavcodec.so.62)
[extra] (stable-mirror.omarchy.org)6.1.0-19 (libavcodec.so.63)

The stable mirror ships ffmpeg 2:9.0.1-4, which provides only the .so.63 family. [omarchy] comes before [extra] in pacman.conf, so pacman installs the [omarchy] build, and that build can't run against stable's own ffmpeg.

The [omarchy] edge repo has no gpu-screen-recorder package, so edge users get Arch's build. Recording worked here until I switched channels.

As of pkgs.omarchy.org/stable/x86_64/omarchy.db last modified Fri, 09 Oct 2026 14:41 GMT, the stable repo still has 5.12.3-2.

Steps to reproduce

  1. Start on the edge channel with a working screen recorder (gpu-screen-recorder 6.1.3-1 from [extra]).
  2. Switch to stable: omarchy channel set stable. Its omarchy-refresh-pacman step runs pacman -Syyuu, which downgrades gpu-screen-recorder 6.1.3-1 -> 5.12.3-2 and ffmpeg 2:9.0.2-2 -> 2:9.0.1-4.
  3. Start a recording, either with omarchy screenrecord --fullscreen or from the Capture menu. It doesn't start.

A fresh stable install probably hits this too, since it would get the same two packages. I haven't tested that.

Expected

The stable channel should ship a gpu-screen-recorder that runs against stable's ffmpeg.

Workaround (verified)

sudo pacman -S extra/gpu-screen-recorder

This installs 6.1.0-1, which links against libavcodec.so.63, libavformat.so.63, libavutil.so.61, libavfilter.so.12 and libswresample.so.7. After that, a test recording with the script's exact arguments produced a valid 3840x2160 H.264 (VAAPI) file. Normal pacman -Syu updates won't downgrade it again, but another channel switch probably will.

Suggested fix

Drop the gpu-screen-recorder pin from the stable [omarchy] repo so stable uses [extra], the way edge does. Or rebuild the pinned package against ffmpeg 9.

View raw text
### System details

AMD Ryzen AI 9 HX 370 (Radeon 890M) + Radeon RX 9060 XT, Omarchy 4.0.4-1, stable channel

### What's wrong?

On the **stable** channel, screen recording doesn't work. `gpu-screen-recorder` exits before it records anything, because it can't load its ffmpeg libraries:

```
$ gpu-screen-recorder -w DP-7 -s 0x0 -k auto -f 60 -fm cfr -fallback-cpu-encoding yes -o test.mp4
gpu-screen-recorder: error while loading shared libraries: libavcodec.so.62: cannot open shared object file: No such file or directory
```

```
$ ldd /usr/bin/gpu-screen-recorder | grep 'not found'
	libavcodec.so.62 => not found
	libavformat.so.62 => not found
	libavutil.so.60 => not found
	libswresample.so.6 => not found
	libavfilter.so.11 => not found
```

`omarchy-capture-screenrecording` fails for both region and fullscreen capture. Its gsr stderr goes to `/dev/null` unless `OMARCHY_SCREENRECORD_DEBUG=true` is set, so from the keybinding or menu the recording just never starts.

**Cause:** in the stable channel, two repos disagree.

| Stable repo | gpu-screen-recorder | ffmpeg it was built against |
|---|---|---|
| `[omarchy]` (`pkgs.omarchy.org/stable`) | **5.12.3-2** | 8 (`libavcodec.so.62`) |
| `[extra]` (`stable-mirror.omarchy.org`) | 6.1.0-1 | 9 (`libavcodec.so.63`) |

The stable mirror ships **ffmpeg 2:9.0.1-4**, which provides only the `.so.63` family. `[omarchy]` comes before `[extra]` in `pacman.conf`, so pacman installs the `[omarchy]` build, and that build can't run against stable's own ffmpeg.

The `[omarchy]` **edge** repo has no `gpu-screen-recorder` package, so edge users get Arch's build. Recording worked here until I switched channels.

As of `pkgs.omarchy.org/stable/x86_64/omarchy.db` last modified Fri, 09 Oct 2026 14:41 GMT, the stable repo still has 5.12.3-2.

### Steps to reproduce

1. Start on the edge channel with a working screen recorder (`gpu-screen-recorder 6.1.3-1` from `[extra]`).
2. Switch to stable: `omarchy channel set stable`. Its `omarchy-refresh-pacman` step runs `pacman -Syyuu`, which downgrades `gpu-screen-recorder 6.1.3-1 -> 5.12.3-2` and `ffmpeg 2:9.0.2-2 -> 2:9.0.1-4`.
3. Start a recording, either with `omarchy screenrecord --fullscreen` or from the Capture menu. It doesn't start.

A fresh stable install probably hits this too, since it would get the same two packages. I haven't tested that.

### Expected

The stable channel should ship a `gpu-screen-recorder` that runs against stable's ffmpeg.

### Workaround (verified)

```
sudo pacman -S extra/gpu-screen-recorder
```

This installs 6.1.0-1, which links against `libavcodec.so.63`, `libavformat.so.63`, `libavutil.so.61`, `libavfilter.so.12` and `libswresample.so.7`. After that, a test recording with the script's exact arguments produced a valid 3840x2160 H.264 (VAAPI) file. Normal `pacman -Syu` updates won't downgrade it again, but another channel switch probably will.

### Suggested fix

Drop the `gpu-screen-recorder` pin from the stable `[omarchy]` repo so stable uses `[extra]`, the way edge does. Or rebuild the pinned package against ffmpeg 9.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 23:52 UTC