Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
system-sleep force-igpu fails on every resume on machines without an NVIDIA dGPU
Reported by neiaki · filed Sep 19, 2026 · open at source
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
What happened
On every resume, /usr/lib/systemd/system-sleep/force-igpu fails:
systemd-sleep[XXXX]: Could not confirm the GPU transition to Vfio mode
(system-sleep)[XXXX]: '/usr/lib/systemd/system-sleep/force-igpu' failed with exit status 1.4 occurrences this boot (one per resume). The marker /run/omarchy-force-igpu-integrated is left behind since the script exits before rm.
Why
This machine has no NVIDIA dGPU at all (Intel-only ThinkPad T480s: lspci -d 10de: empty, omarchy hw nvidia and omarchy hw hybrid gpu both exit 1). But the script runs anyway because its only preconditions are /usr/bin/supergfxctl existing and /etc/supergfxd.conf set to Integrated — both true on a default Omarchy install.
On resume (post), it calls switch_mode Vfio and polls supergfxctl -g for Vfio for 10s. With no dGPU to bind, the mode never becomes Vfio (supergfxd briefly logs LoadVfioDrivers/UnloadVfioDrivers, current mode stays Integrated), so confirmation fails and the script exits 1.
Expected
The script should skip machines without an NVIDIA dGPU (e.g. check for a 10de: PCI device or supergfxd-managed GPU) instead of failing loudly on every resume.
Repro
- Intel-only machine with supergfxd installed and
supergfxd.confmodeIntegrated. - Suspend/resume; check
journalctl -b | grep force-igpu.
System
- Omarchy 4.0.4-1, kernel 7.2.3-arch1-3
- Lenovo ThinkPad T480s (20L8S46L07), Intel UHD Graphics 620 only
- supergfxd active,
supergfxctl -greportsIntegrated
View raw text
## What happened On every resume, `/usr/lib/systemd/system-sleep/force-igpu` fails: ``` systemd-sleep[XXXX]: Could not confirm the GPU transition to Vfio mode (system-sleep)[XXXX]: '/usr/lib/systemd/system-sleep/force-igpu' failed with exit status 1. ``` 4 occurrences this boot (one per resume). The marker `/run/omarchy-force-igpu-integrated` is left behind since the script exits before `rm`. ## Why This machine has no NVIDIA dGPU at all (Intel-only ThinkPad T480s: `lspci -d 10de:` empty, `omarchy hw nvidia` and `omarchy hw hybrid gpu` both exit 1). But the script runs anyway because its only preconditions are `/usr/bin/supergfxctl` existing and `/etc/supergfxd.conf` set to `Integrated` — both true on a default Omarchy install. On resume (`post`), it calls `switch_mode Vfio` and polls `supergfxctl -g` for `Vfio` for 10s. With no dGPU to bind, the mode never becomes `Vfio` (supergfxd briefly logs LoadVfioDrivers/UnloadVfioDrivers, current mode stays `Integrated`), so confirmation fails and the script exits 1. ## Expected The script should skip machines without an NVIDIA dGPU (e.g. check for a `10de:` PCI device or supergfxd-managed GPU) instead of failing loudly on every resume. ## Repro 1. Intel-only machine with supergfxd installed and `supergfxd.conf` mode `Integrated`. 2. Suspend/resume; check `journalctl -b | grep force-igpu`. ## System - Omarchy 4.0.4-1, kernel 7.2.3-arch1-3 - Lenovo ThinkPad T480s (20L8S46L07), Intel UHD Graphics 620 only - supergfxd active, `supergfxctl -g` reports `Integrated`
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 15:51 UTC