Proof Portal

Sign in
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-1740GitHub issuePublicDecided· Out of scope

screenrecord: NVENC fallback doesn't trigger on API version mismatch (Pascal/580xx driver)

Reported by ricardomillerjr · filed Aug 17, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 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

screenrecord: NVENC fallback doesn't trigger on API version mismatch (Pascal/580xx driver)revision 1 · captured 2026-09-28 21:29 UTC via poll

What happened

omarchy screenrecord (any variant — no audio, desktop audio, mic, webcam) fails to start recording. The bar's recording indicator never activates.

Expected

omarchy-capture-screenrecording already passes -fallback-cpu-encoding yes to gpu-screen-recorder, so it should transparently fall back to software encoding when hardware NVENC is unavailable.

Root cause

  • GPU: NVIDIA GeForce GTX 1070 Ti (Pascal/GP104), driver 580.178.04 via nvidia-580xx-dkms — the legacy driver branch required for Pascal GPUs (marked legacy-active, EOL ~2028-09)
  • gpu-screen-recorder 6.0.0 requires NVENC API 13.1; this driver only reports API 13.0 (needs driver 610.00+, which the 580xx legacy branch doesn't offer for Pascal)
  • -fallback-cpu-encoding yes does not trigger for this specific failure — gpu-screen-recorder exits outright with Could not open video codec: Function not implemented instead of retrying with -encoder cpu

I confirmed CPU/software encoding works correctly when forced manually with -encoder cpu (produced a valid clip), so this is a fallback-detection gap rather than a real incompatibility — any Pascal-class NVIDIA GPU on the legacy driver branch would hit this.

Steps to reproduce

  1. On a system with an NVIDIA GPU whose driver reports NVENC API < 13.1 (e.g. Pascal on the 580xx legacy branch)
  2. Run omarchy screenrecord --fullscreen (or pick any option from the Screenrecord menu)
  3. Recording never starts

System info

  • Omarchy: 4.0.0-1
  • Hyprland: 0.56.2
  • gpu-screen-recorder: 6.0.0-1
  • GPU: NVIDIA GeForce GTX 1070 Ti (GP104, Pascal), driver 580.178.04 (nvidia-580xx-dkms)
  • CPU: Intel Core i9-14900K

Debug log (OMARCHY_SCREENRECORD_DEBUG=true)

===== 2026-08-17 11:29:05 args:  target: monitor:DP-2 =====
gsr info: gsr_kms_client_init: setting up connection to /usr/bin/gsr-kms-server
gsr info: gsr_kms_client_init: waiting for server to connect
kms server info: connecting to the client
gsr info: gsr_kms_client_init: server connected
gsr info: replacing file-backed unix domain socket with socketpair
kms server info: connected to the client
gsr info: using socketpair
gsr info: using h264 encoder because a codec was not specified
[h264_nvenc @ 0x557b3650a880] ignoring invalid SAR: 0/0
[h264_nvenc @ 0x557b3650a880] Driver does not support the required nvenc API version. Required: 13.1 Found: 13.0
[h264_nvenc @ 0x557b3650a880] The minimum required Nvidia driver for nvenc is 610.00 or newer
gsr error: Could not open video codec: Function not implemented

Suggested fix

This looks like a fallback-detection bug in gpu-screen-recorder itself (it isn't honoring -fallback-cpu-encoding yes for this particular ffmpeg-level failure). A workaround on Omarchy's side: have omarchy-capture-screenrecording catch this specific stderr pattern (or pre-check NVENC capability) and retry with -encoder cpu explicitly. This may also be worth reporting upstream to gpu-screen-recorder directly.

View raw text
## What happened

`omarchy screenrecord` (any variant — no audio, desktop audio, mic, webcam) fails to start recording. The bar's recording indicator never activates.

## Expected

`omarchy-capture-screenrecording` already passes `-fallback-cpu-encoding yes` to `gpu-screen-recorder`, so it should transparently fall back to software encoding when hardware NVENC is unavailable.

## Root cause

- GPU: NVIDIA GeForce GTX 1070 Ti (Pascal/GP104), driver 580.178.04 via `nvidia-580xx-dkms` — the legacy driver branch required for Pascal GPUs (marked `legacy-active`, EOL ~2028-09)
- `gpu-screen-recorder` 6.0.0 requires NVENC API 13.1; this driver only reports API 13.0 (needs driver 610.00+, which the 580xx legacy branch doesn't offer for Pascal)
- `-fallback-cpu-encoding yes` does not trigger for this specific failure — `gpu-screen-recorder` exits outright with `Could not open video codec: Function not implemented` instead of retrying with `-encoder cpu`

I confirmed CPU/software encoding works correctly when forced manually with `-encoder cpu` (produced a valid clip), so this is a fallback-detection gap rather than a real incompatibility — any Pascal-class NVIDIA GPU on the legacy driver branch would hit this.

## Steps to reproduce

1. On a system with an NVIDIA GPU whose driver reports NVENC API < 13.1 (e.g. Pascal on the 580xx legacy branch)
2. Run `omarchy screenrecord --fullscreen` (or pick any option from the Screenrecord menu)
3. Recording never starts

## System info

- Omarchy: 4.0.0-1
- Hyprland: 0.56.2
- gpu-screen-recorder: 6.0.0-1
- GPU: NVIDIA GeForce GTX 1070 Ti (GP104, Pascal), driver 580.178.04 (nvidia-580xx-dkms)
- CPU: Intel Core i9-14900K

## Debug log (`OMARCHY_SCREENRECORD_DEBUG=true`)

```
===== 2026-08-17 11:29:05 args:  target: monitor:DP-2 =====
gsr info: gsr_kms_client_init: setting up connection to /usr/bin/gsr-kms-server
gsr info: gsr_kms_client_init: waiting for server to connect
kms server info: connecting to the client
gsr info: gsr_kms_client_init: server connected
gsr info: replacing file-backed unix domain socket with socketpair
kms server info: connected to the client
gsr info: using socketpair
gsr info: using h264 encoder because a codec was not specified
[h264_nvenc @ 0x557b3650a880] ignoring invalid SAR: 0/0
[h264_nvenc @ 0x557b3650a880] Driver does not support the required nvenc API version. Required: 13.1 Found: 13.0
[h264_nvenc @ 0x557b3650a880] The minimum required Nvidia driver for nvenc is 610.00 or newer
gsr error: Could not open video codec: Function not implemented
```

## Suggested fix

This looks like a fallback-detection bug in `gpu-screen-recorder` itself (it isn't honoring `-fallback-cpu-encoding yes` for this particular ffmpeg-level failure). A workaround on Omarchy's side: have `omarchy-capture-screenrecording` catch this specific stderr pattern (or pre-check NVENC capability) and retry with `-encoder cpu` explicitly. This may also be worth reporting upstream to gpu-screen-recorder directly.

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 04:31 UTC