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

omarchy-update doesn't offer a reboot after an NVIDIA driver update, so the old driver stays loaded

Reported by slogonomo · filed Oct 10, 2026 · open at source

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

omarchy-update doesn't offer a reboot after an NVIDIA driver update, so the old driver stays loadedrevision 1 · captured 2026-10-10 14:00 UTC via poll

What happened

omarchy-update (2026-10-10) upgraded nvidia-utils/nvidia-open-dkms from 615.71.09 to 615.78.08, with no kernel change, and finished without offering a reboot. The old kernel module stayed loaded (/proc/driver/nvidia/version still reports 615.71.09), so nvidia-smi fails with:

Failed to initialize NVML: Driver/library version mismatch
NVML library version: 615.78

GPU apps started after the update can't use the NVIDIA driver. mpv aborted at startup on every file (SIGABRT, assertion !vo->x11 in vo_x11_init, reached from ra_ctx_create → mpegl_init while it tried fallback GPU contexts). Mesa's libgallium was loaded in the process in place of the NVIDIA driver.

Expected

A reboot prompt, the same as after a kernel update.

Cause

omarchy-update-restart only prompts when the running kernel has been replaced, when ~/.local/state/omarchy/reboot-required exists, or when the Hyprland binary has been replaced. An NVIDIA driver update triggers none of these.

Steps to reproduce

  1. On an NVIDIA machine, run omarchy-update when a new nvidia-utils/nvidia-open-dkms is available but the kernel isn't changing.
  2. No reboot is offered.
  3. nvidia-smi reports a version mismatch, and newly launched GPU apps (e.g. mpv) fail until you reboot.

Possible fix

If /proc/driver/nvidia/version exists, compare its version with pacman -Q nvidia-utils and offer a reboot when they differ. Alternatively, add a pacman hook on nvidia-utils that sets reboot-required.

System

  • Omarchy 4.0.0.r6863.ga15636b-1 (edge channel)
  • Kernel 7.2.8-5-omarchy-bore
  • GeForce RTX 3080 Ti (GA102), nvidia-open-dkms / nvidia-utils 615.78.08-1 installed, 615.71.09 module loaded
  • mpv 1:0.41.0-6, mesa 1:26.2.4-1

omarchy debug isn't available in this build, so the details above were collected by hand.

Filed by Claude Opus 5.5 via Claude Code.

View raw text
**What happened**

`omarchy-update` (2026-10-10) upgraded `nvidia-utils`/`nvidia-open-dkms` from 615.71.09 to 615.78.08, with no kernel change, and finished without offering a reboot. The old kernel module stayed loaded (`/proc/driver/nvidia/version` still reports 615.71.09), so `nvidia-smi` fails with:

```
Failed to initialize NVML: Driver/library version mismatch
NVML library version: 615.78
```

GPU apps started after the update can't use the NVIDIA driver. mpv aborted at startup on every file (SIGABRT, assertion `!vo->x11` in `vo_x11_init`, reached from `ra_ctx_create` → `mpegl_init` while it tried fallback GPU contexts). Mesa's `libgallium` was loaded in the process in place of the NVIDIA driver.

**Expected**

A reboot prompt, the same as after a kernel update.

**Cause**

`omarchy-update-restart` only prompts when the running kernel has been replaced, when `~/.local/state/omarchy/reboot-required` exists, or when the Hyprland binary has been replaced. An NVIDIA driver update triggers none of these.

**Steps to reproduce**

1. On an NVIDIA machine, run `omarchy-update` when a new `nvidia-utils`/`nvidia-open-dkms` is available but the kernel isn't changing.
2. No reboot is offered.
3. `nvidia-smi` reports a version mismatch, and newly launched GPU apps (e.g. mpv) fail until you reboot.

**Possible fix**

If `/proc/driver/nvidia/version` exists, compare its version with `pacman -Q nvidia-utils` and offer a reboot when they differ. Alternatively, add a pacman hook on `nvidia-utils` that sets `reboot-required`.

**System**

- Omarchy 4.0.0.r6863.ga15636b-1 (edge channel)
- Kernel 7.2.8-5-omarchy-bore
- GeForce RTX 3080 Ti (GA102), nvidia-open-dkms / nvidia-utils 615.78.08-1 installed, 615.71.09 module loaded
- mpv 1:0.41.0-6, mesa 1:26.2.4-1

`omarchy debug` isn't available in this build, so the details above were collected by hand.

Filed by Claude Opus 5.5 via Claude Code.

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-10 14:59 UTC