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.
Touchscreen input registers on all connected monitors instead of only the laptop display
Reported by JackRubiralta · filed Apr 16, 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
Dell Pro Max 14 Premium MA10, Intel(R) Core(TM) Ultra 9, NVIDIA RTX PRO 2000 Blackwell / Intel Arc Pro 130T/140T, 2880x1800 @ 2x in 14", 60Hz (laptop) + external monitor(s), Omarchy 3.5.0
What's wrong?
When using the touchscreen on my laptop in a multi-monitor setup, touch input is not constrained to the laptop's built-in display. Instead, touch events appear to be mapped across the entire combined output region, so tapping on the laptop screen also triggers clicks/input on the connected external monitor(s).
Expected behavior: Touch input on the laptop's built-in touchscreen should only control the cursor/clicks on the laptop display.
Actual behavior: Touch input is spread across all connected displays, making the touchscreen effectively unusable when external monitors are connected.
View raw text
### System details Dell Pro Max 14 Premium MA10, Intel(R) Core(TM) Ultra 9, NVIDIA RTX PRO 2000 Blackwell / Intel Arc Pro 130T/140T, 2880x1800 @ 2x in 14", 60Hz (laptop) + external monitor(s), Omarchy 3.5.0 ### What's wrong? When using the touchscreen on my laptop in a multi-monitor setup, touch input is not constrained to the laptop's built-in display. Instead, touch events appear to be mapped across the entire combined output region, so tapping on the laptop screen also triggers clicks/input on the connected external monitor(s). Expected behavior: Touch input on the laptop's built-in touchscreen should only control the cursor/clicks on the laptop display. Actual behavior: Touch input is spread across all connected displays, making the touchscreen effectively unusable when external monitors are connected.
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 02:51 UTC