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.
Haptic touchpad not working on XPS 2026 with Synaptics 06CB:D01D
Reported by Capisia-yhi · filed Apr 14, 2026Closed upstream on 2026-04-15 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
Summary
The haptic touchpad fix introduced in v3.5.0 does not work on Dell XPS 2026 units with the Synaptics 06CB:D01D controller. The fix targets 06CB:D01A, which causes the daemon to crash-loop with "No Synaptics haptic touchpad hidraw device found" on D01D hardware.
Environment
- Omarchy version: 3.5.0
- Machine: Dell XPS 2026 (Intel Panther Lake)
- Touchpad HID device:
06CB:D01D(vs.06CB:D01Atargeted by the fix)
HID_ID=0018:000006CB:0000D01D
HID_NAME=VEN_06CB:00 06CB:D01D
DRIVER=hid-multitouchWhat happens
With the product ID patched to D01D, the daemon starts and finds the device correctly:
Haptic touchpad: hidraw=/dev/hidraw0 input=/dev/input/event8 intensity=40The HIDIOCSFEATURE ioctl on REPORT_ID=0x37 executes without error, but no haptic feedback is felt.
Diagnosis
The HID descriptor of the D01D confirms that REPORT_ID=0x37 exists (Haptics Usage Page 0x0E, Usage 0x23 — Waveform Vendor Page, 8-bit, range 0–100), identical in structure to D01A. However, the ioctl silently has no effect on D01D hardware.
This suggests the D01D firmware requires either:
- A different REPORT_ID to trigger the haptic actuator, or
- A different report format (e.g., more bytes, different structure)
Additional findings:
- Hyprland does not use EVIOCGRAB on the touchpad — root can read event8 directly
- ABS_MT_PRESSURE and ABS_PRESSURE are exposed on event8
- The hardware button bit (byte[39] in Report 0x03) is always 0 — physical clicks are not reflected as a HID button bit; they are detected by the kernel via pressure/ISH
Workaround
None currently. The daemon runs but produces no haptic output on D01D.
Suggested fix
The product ID list in omarchy-haptic-touchpad should include D01D once the correct report format for D01D is identified. The fix likely requires reverse-engineering the D01D firmware or testing alternative REPORT_IDs from the HID descriptor.
Other feature reports present on the D01D that could be candidates:
- 0x08 — Feature, Digitizer page
- 0x0D — Feature, Digitizer page
- 0x50 — Feature, vendor page (FF00)
- 0x0F, 0x0E, 0x22 — Feature, vendor page
Happy to test patches if proposed.
View raw text
## Summary The haptic touchpad fix introduced in v3.5.0 does not work on Dell XPS 2026 units with the Synaptics **06CB:D01D** controller. The fix targets **06CB:D01A**, which causes the daemon to crash-loop with "No Synaptics haptic touchpad hidraw device found" on D01D hardware. ## Environment - Omarchy version: 3.5.0 - Machine: Dell XPS 2026 (Intel Panther Lake) - Touchpad HID device: `06CB:D01D` (vs. `06CB:D01A` targeted by the fix) ``` HID_ID=0018:000006CB:0000D01D HID_NAME=VEN_06CB:00 06CB:D01D DRIVER=hid-multitouch ``` ## What happens With the product ID patched to `D01D`, the daemon starts and finds the device correctly: ``` Haptic touchpad: hidraw=/dev/hidraw0 input=/dev/input/event8 intensity=40 ``` The `HIDIOCSFEATURE` ioctl on `REPORT_ID=0x37` executes without error, but **no haptic feedback is felt**. ## Diagnosis The HID descriptor of the D01D confirms that `REPORT_ID=0x37` exists (Haptics Usage Page 0x0E, Usage 0x23 — Waveform Vendor Page, 8-bit, range 0–100), identical in structure to D01A. However, the ioctl silently has no effect on D01D hardware. This suggests the D01D firmware requires either: - A **different REPORT_ID** to trigger the haptic actuator, or - A **different report format** (e.g., more bytes, different structure) Additional findings: - Hyprland does **not** use `EVIOCGRAB` on the touchpad — root can read `event8` directly - `ABS_MT_PRESSURE` and `ABS_PRESSURE` are exposed on `event8` - The hardware button bit (byte[39] in Report 0x03) is **always 0** — physical clicks are not reflected as a HID button bit; they are detected by the kernel via pressure/ISH ## Workaround None currently. The daemon runs but produces no haptic output on D01D. ## Suggested fix The product ID list in `omarchy-haptic-touchpad` should include `D01D` once the correct report format for D01D is identified. The fix likely requires reverse-engineering the D01D firmware or testing alternative REPORT_IDs from the HID descriptor. Other feature reports present on the D01D that could be candidates: - `0x08` — Feature, Digitizer page - `0x0D` — Feature, Digitizer page - `0x50` — Feature, vendor page (FF00) - `0x0F`, `0x0E`, `0x22` — Feature, vendor page Happy to test patches if proposed.
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.