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.
Hybrid GPU toggle leaves supergfxd stuck when the NVIDIA module cannot be unloaded
Reported by mohammed-bageri · filed Aug 27, 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
System details
Lenovo laptop, AMD Raphael iGPU, NVIDIA RTX 5060 Laptop GPU, Omarchy 4.0.1-1, Linux 7.1.9-arch1-2, supergfxctl 5.2.7-2, NVIDIA 610.57.04
What's wrong?
I used omarchy toggle hybrid gpu to switch from Hybrid to Integrated mode and rebooted.
After boot, supergfxd was running, but queries hung:
$ timeout 5 supergfxctl -g
# exits with 124The Omarchy toggle reported:
supergfxd is not responding. Try again, or check: systemctl status supergfxdThe relevant service log was:
Did rmmod for driver nvidia_drm
Did rmmod for driver nvidia_modeset
Did rmmod for driver nvidia_uvm
Action thread errored: Modprobe error: rmmod nvidia failed: "rmmod: ERROR: Module nvidia is in use"At that point /etc/supergfxd.conf contained "mode": "Integrated". The NVIDIA device was left partially initialized/unbound and the daemon no longer answered clients.
I recovered by changing the saved mode back to Hybrid, removing the two Integrated-only files below, and rebooting:
/usr/lib/systemd/system-sleep/force-igpu
/etc/systemd/system/supergfxd.service.d/delay-start.confAfter reboot, supergfxctl -g reported Hybrid and nvidia-smi worked normally.
If the NVIDIA modules cannot be unloaded, the toggle should fail without leaving the daemon stuck and the saved configuration halfway switched. It may also be worth checking what is holding the NVIDIA module before committing the Integrated-mode configuration.
Possibly related: #6399 and #5408, although those reports appear to fail at different points.
View raw text
### System details Lenovo laptop, AMD Raphael iGPU, NVIDIA RTX 5060 Laptop GPU, Omarchy 4.0.1-1, Linux 7.1.9-arch1-2, supergfxctl 5.2.7-2, NVIDIA 610.57.04 ### What's wrong? I used `omarchy toggle hybrid gpu` to switch from Hybrid to Integrated mode and rebooted. After boot, `supergfxd` was running, but queries hung: ```console $ timeout 5 supergfxctl -g # exits with 124 ``` The Omarchy toggle reported: ```text supergfxd is not responding. Try again, or check: systemctl status supergfxd ``` The relevant service log was: ```text Did rmmod for driver nvidia_drm Did rmmod for driver nvidia_modeset Did rmmod for driver nvidia_uvm Action thread errored: Modprobe error: rmmod nvidia failed: "rmmod: ERROR: Module nvidia is in use" ``` At that point `/etc/supergfxd.conf` contained `"mode": "Integrated"`. The NVIDIA device was left partially initialized/unbound and the daemon no longer answered clients. I recovered by changing the saved mode back to `Hybrid`, removing the two Integrated-only files below, and rebooting: ```text /usr/lib/systemd/system-sleep/force-igpu /etc/systemd/system/supergfxd.service.d/delay-start.conf ``` After reboot, `supergfxctl -g` reported `Hybrid` and `nvidia-smi` worked normally. If the NVIDIA modules cannot be unloaded, the toggle should fail without leaving the daemon stuck and the saved configuration halfway switched. It may also be worth checking what is holding the NVIDIA module before committing the Integrated-mode configuration. Possibly related: #6399 and #5408, although those reports appear to fail at different points.
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 09:28 UTC