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.
Hardware cursor intermittently stops rendering on hybrid Intel/NVIDIA multi-monitor laptop (recurs despite no_hardware_cursors=true)
Reported by Cousint98 · filed Sep 15, 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 Legion 7 16IRX9, Intel i9-14900HX, Intel UHD Graphics (iGPU) + NVIDIA RTX 4060 Max-Q (hybrid/Optimus), 4 monitors (1 internal eDP + 3 external DP/HDMI), Omarchy 4.0.3-1, Hyprland 0.56.2
What's wrong?
The mouse cursor intermittently stops rendering properly -- goes invisible or renders as a faint/glitchy trail (described as barely visible, "like snow" against some backgrounds) -- on this multi-monitor hybrid-GPU laptop. This is not a one-off: it has recurred repeatedly across a single session.
no_hardware_cursors = true is already set in ~/.config/hypr/looknfeel.lua, so the standard workaround is in place, but the bug still comes back.
What I've tried:
- hyprctl setcursor Adwaita 24 -- fixes it temporarily each time, but it recurs later in the same session.
- hyprctl reload (to force no_hardware_cursors to re-trigger) -- also only temporary.
- Swapped display cables -- no change, which rules out a cable/physical-connection cause and points at the compositor/cursor-plane layer instead.
Reproduction: Not fully deterministic -- happens intermittently during normal use across 4 outputs (1 internal eDP-2 panel + 3 external monitors on DP-2, DP-3, and HDMI-A-1), on a hybrid Intel iGPU (i915) + NVIDIA dGPU (nvidia driver) laptop.
Evidence: Full debug log: https://logs.omarchy.org/jdpVm5 (expires in 24h). I also have a short screen recording taken while the glitch was present and can attach it directly to this issue.
Given the hybrid multi-GPU + multi-monitor setup, this may relate to hardware cursor-plane handling across GPUs/outputs rather than being laptop-model-specific.
View raw text
### System details Lenovo Legion 7 16IRX9, Intel i9-14900HX, Intel UHD Graphics (iGPU) + NVIDIA RTX 4060 Max-Q (hybrid/Optimus), 4 monitors (1 internal eDP + 3 external DP/HDMI), Omarchy 4.0.3-1, Hyprland 0.56.2 ### What's wrong? The mouse cursor intermittently stops rendering properly -- goes invisible or renders as a faint/glitchy trail (described as barely visible, "like snow" against some backgrounds) -- on this multi-monitor hybrid-GPU laptop. This is not a one-off: it has recurred repeatedly across a single session. `no_hardware_cursors = true` is already set in `~/.config/hypr/looknfeel.lua`, so the standard workaround is in place, but the bug still comes back. **What I've tried:** - `hyprctl setcursor Adwaita 24` -- fixes it temporarily each time, but it recurs later in the same session. - `hyprctl reload` (to force `no_hardware_cursors` to re-trigger) -- also only temporary. - Swapped display cables -- no change, which rules out a cable/physical-connection cause and points at the compositor/cursor-plane layer instead. **Reproduction:** Not fully deterministic -- happens intermittently during normal use across 4 outputs (1 internal eDP-2 panel + 3 external monitors on DP-2, DP-3, and HDMI-A-1), on a hybrid Intel iGPU (i915) + NVIDIA dGPU (nvidia driver) laptop. **Evidence:** Full debug log: https://logs.omarchy.org/jdpVm5 (expires in 24h). I also have a short screen recording taken while the glitch was present and can attach it directly to this issue. Given the hybrid multi-GPU + multi-monitor setup, this may relate to hardware cursor-plane handling across GPUs/outputs rather than being laptop-model-specific.
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 13:43 UTC