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.
os.execute() always fails with ECHILD inside Hyprland's embedded Lua config (breaks nvidia.lua auto-detection)
Reported by drumstin · filed Aug 30, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #7755 (R-1582). GitHub close reason: completed.
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
What happened
/usr/share/omarchy/default/hypr/nvidia.lua auto-detects an NVIDIA GPU and is
supposed to export NVD_BACKEND=direct, LIBVA_DRIVER_NAME=nvidia, and__GLX_VENDOR_LIBRARY_NAME=nvidia via hl.env(), gated on o.shell_succeeds().
On this machine, that detection always fails — o.shell_succeeds() calls Lua'sos.execute(), and os.execute() inside Hyprland's embedded Lua config engine
always fails with ECHILD ("No child processes"), for every command, even true.
This means the bug isn't NVIDIA-detection-specific — os.execute() appears to be
broken generically inside Hyprland's Lua config, likely because Hyprland reaps
SIGCHLD itself in its event loop, racing Lua's own waitpid() call.
Consequence for NVIDIA users: Hyprland never gets NVD_BACKEND=direct, so it
doesn't use the fast NVIDIA GSP backend, and hyprctl monitors showshardwareCursorsInUse: false (cursor falls back to software compositing) even
though the driver/GPU fully support hardware cursors. This is a known contributor
to Hyprland+NVIDIA stutter.
Steps to reproduce
- Add a diagnostic line to
~/.config/hypr/autostart.lua:
hl.env(nil, tostring(os.execute("true"))) (or similar — call os.execute("true")
and surface its raw return values)
2. Reload Hyprland
3. Read the result from a freshly spawned child process's /proc/<pid>/environ
4. Result: nil|No child processes|10 — a real ECHILD error, not a "false" logic result
Expected
os.execute("true") should succeed and NVIDIA auto-detection should correctly
export the GSP backend env vars.
System details
- Omarchy 4.0.0-1
- Hyprland launched via UWSM (
[email protected]) - CPU: Intel Arrow Lake-S (iGPU unused for display)
- GPU: NVIDIA RTX 4070 Ti Super (Ada Lovelace, GSP-capable), driver 610.57.04
- Single monitor via DisplayPort, 1920x1080@144Hz VRR
Workaround in use
Manually exporting the three vars in ~/.config/uwsm/env-hyprland so they're set
by UWSM before Hyprland/Aquamarine launches (before nvidia.lua's broken detection
would even run). This works but bypasses the intended auto-detection entirely.
View raw text
### What happened
`/usr/share/omarchy/default/hypr/nvidia.lua` auto-detects an NVIDIA GPU and is
supposed to export `NVD_BACKEND=direct`, `LIBVA_DRIVER_NAME=nvidia`, and
`__GLX_VENDOR_LIBRARY_NAME=nvidia` via `hl.env()`, gated on `o.shell_succeeds()`.
On this machine, that detection always fails — `o.shell_succeeds()` calls Lua's
`os.execute()`, and `os.execute()` inside Hyprland's embedded Lua config engine
always fails with `ECHILD` ("No child processes"), for *every* command, even `true`.
This means the bug isn't NVIDIA-detection-specific — `os.execute()` appears to be
broken generically inside Hyprland's Lua config, likely because Hyprland reaps
SIGCHLD itself in its event loop, racing Lua's own `waitpid()` call.
Consequence for NVIDIA users: Hyprland never gets `NVD_BACKEND=direct`, so it
doesn't use the fast NVIDIA GSP backend, and `hyprctl monitors` shows
`hardwareCursorsInUse: false` (cursor falls back to software compositing) even
though the driver/GPU fully support hardware cursors. This is a known contributor
to Hyprland+NVIDIA stutter.
### Steps to reproduce
1. Add a diagnostic line to `~/.config/hypr/autostart.lua`:
`hl.env(nil, tostring(os.execute("true")))` (or similar — call `os.execute("true")`
and surface its raw return values)
2. Reload Hyprland
3. Read the result from a freshly spawned child process's `/proc/<pid>/environ`
4. Result: `nil|No child processes|10` — a real ECHILD error, not a "false" logic result
### Expected
`os.execute("true")` should succeed and NVIDIA auto-detection should correctly
export the GSP backend env vars.
### System details
- Omarchy 4.0.0-1
- Hyprland launched via UWSM (`[email protected]`)
- CPU: Intel Arrow Lake-S (iGPU unused for display)
- GPU: NVIDIA RTX 4070 Ti Super (Ada Lovelace, GSP-capable), driver 610.57.04
- Single monitor via DisplayPort, 1920x1080@144Hz VRR
### Workaround in use
Manually exporting the three vars in `~/.config/uwsm/env-hyprland` so they're set
by UWSM before Hyprland/Aquamarine launches (before nvidia.lua's broken detection
would even run). This works but bypasses the intended auto-detection entirely.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.