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

screenrecording --with-webcam: mpv webcam overlay crashes with SIGSEGV in Mesa/libplacebo on Apple Silicon (needs --vo=gpu fallback)

Reported by marceloid · filed Aug 26, 2026Closed upstream on 2026-10-08 by the bot omarchybot, as not planned.

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

screenrecording --with-webcam: mpv webcam overlay crashes with SIGSEGV in Mesa/libplacebo on Apple Silicon (needs --vo=gpu fallback)revision 1 · captured 2026-09-28 21:24 UTC via poll

What happened?

When starting a screen recording with webcam overlay on Apple Silicon (omarchy-capture-screenrecording --with-webcam), the WebcamOverlay mpv process crashes with SIGSEGV within ~10 seconds.

Root Cause & Evidence

mpv's default vo=gpu-next (libplacebo) attempts texture plane uploads (pl_tex_upload / pl_upload_plane) that trigger a SEGV_MAPERR memcpy segfault inside the Mesa Asahi drivers (libvulkan_asahi.so under Vulkan, libgallium-26.1.7.so under OpenGL).

Stack trace excerpt (PID 109482):

#0  0x0000ffff7c58ddd8 memcpy (libc.so.6)
#1  0x0000ffff5ac6a264 (libgallium-26.1.7.so)
#2  0x0000ffff7e00e474 (libplacebo.so.360)
#4  pl_tex_upload (libplacebo.so.360)
#5  pl_upload_plane (libplacebo.so.360)

Proposed Fix

omarchy-capture-screenrecording already detects Apple Silicon to select wf-recorder. Adding --vo=gpu to the mpv invocation in start_webcam_overlay() (or setting it conditionally on Apple hardware) avoids vo=gpu-next and resolves the crash completely.

System Details

  • Hardware: Apple Silicon (aarch64)
  • Omarchy version: 4.0.0-1
  • Mesa version: 26.1.7-1
  • mpv version: 0.41.0-4
Filed by gemini-3.7-flash via pi.
View raw text
### What happened?
When starting a screen recording with webcam overlay on Apple Silicon (`omarchy-capture-screenrecording --with-webcam`), the `WebcamOverlay` mpv process crashes with SIGSEGV within ~10 seconds.

### Root Cause & Evidence
mpv's default `vo=gpu-next` (`libplacebo`) attempts texture plane uploads (`pl_tex_upload` / `pl_upload_plane`) that trigger a `SEGV_MAPERR` `memcpy` segfault inside the Mesa Asahi drivers (`libvulkan_asahi.so` under Vulkan, `libgallium-26.1.7.so` under OpenGL).

Stack trace excerpt (PID 109482):
```
#0  0x0000ffff7c58ddd8 memcpy (libc.so.6)
#1  0x0000ffff5ac6a264 (libgallium-26.1.7.so)
#2  0x0000ffff7e00e474 (libplacebo.so.360)
#4  pl_tex_upload (libplacebo.so.360)
#5  pl_upload_plane (libplacebo.so.360)
```

### Proposed Fix
`omarchy-capture-screenrecording` already detects Apple Silicon to select `wf-recorder`. Adding `--vo=gpu` to the `mpv` invocation in `start_webcam_overlay()` (or setting it conditionally on Apple hardware) avoids `vo=gpu-next` and resolves the crash completely.

### System Details
- Hardware: Apple Silicon (aarch64)
- Omarchy version: 4.0.0-1
- Mesa version: 26.1.7-1
- mpv version: 0.41.0-4

> Filed by gemini-3.7-flash via pi.

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.