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

omarchy-install-gaming-steam pulls nvidia-utils onto non-NVIDIA systems: --noconfirm picks lib32-nvidia-utils for steam's lib32-vulkan-driver dep

Reported by microfire21-og · filed Aug 29, 2026Closed upstream on 2026-10-04 by the merge of PR #12569 (closed by dhh). GitHub close reason: completed.

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

omarchy-install-gaming-steam pulls nvidia-utils onto non-NVIDIA systems: --noconfirm picks lib32-nvidia-utils for steam's lib32-vulkan-driver deprevision 1 · captured 2026-09-28 21:24 UTC via poll

omarchy-install-gaming-steam installs Steam before the GPU-aware driver step, so pacman's --noconfirm provider auto-pick wins the race:

# bin/omarchy-install-gaming-steam
omarchy-pkg-add steam                 # -> pacman -S --noconfirm --needed steam
omarchy-install-gaming-gpu-lib32      # correct and GPU-aware, but runs second

steam depends on the virtual lib32-vulkan-driver. Under --noconfirm pacman takes the first provider in repo order — lib32-nvidia-utils — which hard-depends on nvidia-utils. So the NVIDIA userspace stack gets installed on machines with no NVIDIA GPU.

From /var/log/pacman.log on an AMD-only laptop (Ryzen 9 7940HS / Radeon 780M, no dGPU):

10:57:02  pacman -S --noconfirm --needed steam
10:57:48  installed nvidia-utils (610.57.04-1)
10:57:53  installed lib32-nvidia-utils (610.57.04-1)
10:58:01  pacman -S --noconfirm --needed lib32-vulkan-radeon   <- 8 seconds too late

Detection itself is not at fault: omarchy-hw-nvidia-gsp and omarchy-hw-nvidia-without-gsp both correctly exit 1 on this hardware, and omarchy-install-gaming-gpu-lib32 correctly installed only lib32-vulkan-radeon. It just runs after the damage is done.

Why it matters. nvidia-utils ships /usr/share/glvnd/egl_vendor.d/10_nvidia.json, which libglvnd ranks ahead of Mesa's 50_mesa.json, plus the egl_external_platform.d entries. On this machine that produces a reproducible SIGSEGV in Brave's GPU process:

#0  pthread_mutex_lock            (libc.so.6)
#1  wl_proxy_create_wrapper       (libwayland-client.so.0)
#2  libnvidia-egl-wayland2.so.1 + 0x9b1a
#5  libEGL_nvidia.so.0 + 0xab0f9
#7  libEGL.so.1 + 0x625e

rdi at the fault is 0x133 — offsetof(wl_display, mutex) off a NULL display — byte-identical across four separate cores, so it is a deterministic null deref in NVIDIA's EGL wayland2 platform, not corruption. 11 crashes over 5 days; Chromium eventually hit its GPU-crash threshold and permanently set --use-gl=disabled, dropping the browser to software rendering.

Suggested fix: run omarchy-install-gaming-gpu-lib32 before omarchy-pkg-add steam, or pass the resolved provider explicitly so --noconfirm has nothing to guess.

Related but distinct: #6216 also lands in this path, via the detector regex rather than provider order.

omarchy 4.0.1-1, linux 7.1.9.arch1-2. Skipping a full omarchy debug dump since this is a one-off script-ordering bug — happy to add it if useful.

Filed by Claude Opus 5 via Claude Code CLI.

View raw text
`omarchy-install-gaming-steam` installs Steam before the GPU-aware driver step, so pacman's `--noconfirm` provider auto-pick wins the race:

```bash
# bin/omarchy-install-gaming-steam
omarchy-pkg-add steam                 # -> pacman -S --noconfirm --needed steam
omarchy-install-gaming-gpu-lib32      # correct and GPU-aware, but runs second
```

`steam` depends on the virtual `lib32-vulkan-driver`. Under `--noconfirm` pacman takes the first provider in repo order — `lib32-nvidia-utils` — which hard-depends on `nvidia-utils`. So the NVIDIA userspace stack gets installed on machines with no NVIDIA GPU.

From `/var/log/pacman.log` on an AMD-only laptop (Ryzen 9 7940HS / Radeon 780M, no dGPU):

```
10:57:02  pacman -S --noconfirm --needed steam
10:57:48  installed nvidia-utils (610.57.04-1)
10:57:53  installed lib32-nvidia-utils (610.57.04-1)
10:58:01  pacman -S --noconfirm --needed lib32-vulkan-radeon   <- 8 seconds too late
```

Detection itself is not at fault: `omarchy-hw-nvidia-gsp` and `omarchy-hw-nvidia-without-gsp` both correctly exit 1 on this hardware, and `omarchy-install-gaming-gpu-lib32` correctly installed only `lib32-vulkan-radeon`. It just runs after the damage is done.

**Why it matters.** `nvidia-utils` ships `/usr/share/glvnd/egl_vendor.d/10_nvidia.json`, which libglvnd ranks ahead of Mesa's `50_mesa.json`, plus the `egl_external_platform.d` entries. On this machine that produces a reproducible SIGSEGV in Brave's GPU process:

```
#0  pthread_mutex_lock            (libc.so.6)
#1  wl_proxy_create_wrapper       (libwayland-client.so.0)
#2  libnvidia-egl-wayland2.so.1 + 0x9b1a
#5  libEGL_nvidia.so.0 + 0xab0f9
#7  libEGL.so.1 + 0x625e
```

`rdi` at the fault is `0x133` — `offsetof(wl_display, mutex)` off a NULL `display` — byte-identical across four separate cores, so it is a deterministic null deref in NVIDIA's EGL wayland2 platform, not corruption. 11 crashes over 5 days; Chromium eventually hit its GPU-crash threshold and permanently set `--use-gl=disabled`, dropping the browser to software rendering.

**Suggested fix:** run `omarchy-install-gaming-gpu-lib32` before `omarchy-pkg-add steam`, or pass the resolved provider explicitly so `--noconfirm` has nothing to guess.

Related but distinct: #6216 also lands in this path, via the detector regex rather than provider order.

omarchy 4.0.1-1, linux 7.1.9.arch1-2. Skipping a full `omarchy debug` dump since this is a one-off script-ordering bug — happy to add it if useful.

Filed by Claude Opus 5 via Claude Code CLI.

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.