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.
omarchy toggle touchpad fails to detect touchpads like synaptics-tm3096-006
Reported by vicXvac · filed Sep 2, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #8376 (R-1426). 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
Omarchy version: 4.0.2-1
What happened: omarchy toggle touchpad does nothing — the touchpad stays enabled.
Expected: omarchy toggle touchpad off (or toggle) should disable the touchpad.
Steps to reproduce:
1. Run omarchy-hw-touchpad → prints nothing
2. Run omarchy toggle touchpad off → touches still work on the touchpad; no OSD shown
Root cause: omarchy-hw-touchpad (the device detector used by the toggle) selects only mice whose name matches touchpad|trackpad:
hyprctl devices -j | jq -r '[.mice[] | .name | select(test("touchpad|trackpad"; "i"))] | first // empty'My touchpad enumerates as synaptics-tm3096-006 (under hyprctl devices → mice), which matches neither touchpad nor trackpad, so no device is found and omarchy-toggle-input-device exits with "No touchpad device found".
Many common touchpads use vendor/controller names (synaptics, elan, alps, focal) rather than the literal words "touchpad"/"trackpad", so this is likely to affect a wide range of hardware. The .touch[] category in hyprctl devices is also a more reliable source for true touchpads where present.
System: Arch Linux, Omarchy 4.0.2-1
View raw text
**Omarchy version:** 4.0.2-1
**What happened:** `omarchy toggle touchpad` does nothing — the touchpad stays enabled.
**Expected:** `omarchy toggle touchpad off` (or `toggle`) should disable the touchpad.
**Steps to reproduce:**
1. Run `omarchy-hw-touchpad` → prints nothing
2. Run `omarchy toggle touchpad off` → touches still work on the touchpad; no OSD shown
**Root cause:** `omarchy-hw-touchpad` (the device detector used by the toggle) selects only mice whose name matches `touchpad|trackpad`:
```bash
hyprctl devices -j | jq -r '[.mice[] | .name | select(test("touchpad|trackpad"; "i"))] | first // empty'
```
My touchpad enumerates as `synaptics-tm3096-006` (under `hyprctl devices` → `mice`), which matches neither `touchpad` nor `trackpad`, so no device is found and `omarchy-toggle-input-device` exits with "No touchpad device found".
Many common touchpads use vendor/controller names (synaptics, elan, alps, focal) rather than the literal words "touchpad"/"trackpad", so this is likely to affect a wide range of hardware. The `.touch[]` category in `hyprctl devices` is also a more reliable source for true touchpads where present.
**System:** Arch Linux, Omarchy 4.0.2-1Validation
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.