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.
Huawei BOD-WXX9 (Goodix GXTP7863 27C6:01E0): touchpad ignores all input on a fresh install
Reported by SemihMutlu07 · filed Aug 31, 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
Intel i7-1165G7, Intel Iris Xe, Huawei MateBook D (BOD-WXX9 / BOD-WXX9-PCB-B3, BIOS 2.31), Omarchy 4.0.1-1 (Hyprland 0.56.2, kernel 7.1.9-arch1-2)
What's wrong?
On a fresh Omarchy install, the built-in touchpad on this Huawei MateBook D produced no pointer motion, scrolling, or taps. The rest of the desktop came up normally; the failure was specific to the internal pad.
Cause (from the install-day journal, not from a later healthy boot): the kernel's i2c_hid_acpi probe for i2c-GXTP7863:00 fails with `-110` (`ETIMEDOUT`). On those boots there is no GXTP input node at all, so Omarchy / Hyprland / libinput have nothing to configure. This is not an omarchy-hw-touchpad name-matching miss.
Version (from install logs, not guessed):
- ISO / installer on 2026-08-25 shipped
omarchy 4.0.0-1(omarchy-settings 4.0.0-1). That matches downloading “the current ISO” before v4.0.1 existed (v4.0.0 was 2026-08-14; v4.0.1 published 2026-08-25 11:24 UTC). - The first
pacman -Syuthe same evening upgradedomarchy4.0.0-1→4.0.1-1(22:38 +03). - First boot was one minute later (22:39 +03), so the first graphical session — and this machine still — is Omarchy 4.0.1-1. I am not claiming this was a 4.0.1 ISO.
Steps to reproduce
- Fresh-install Omarchy from the 4.0.0 ISO on a Huawei BOD-WXX9 (MateBook D); first boot after the installer’s online update to 4.0.1.
- Reach the desktop / lock screen without adding user
input.luaor libinput quirks. - Use the built-in touchpad: move, tap-to-click, two-finger scroll.
Expected
The internal Goodix pad works as a touchpad out of the box (move, tap, scroll).
Actual
The pad does not register those inputs. Kernel log on the failed boots:
i2c_hid_acpi i2c-GXTP7863:00: can't add hid device: -110
i2c_hid_acpi i2c-GXTP7863:00: probe with driver i2c_hid_acpi failed with error -110Per-boot journal (including the later successful bind) is in the comment below.
Hardware
| DMI | HUAWEI BOD-WXX9 (family: MateBook D, board: BOD-WXX9-PCB-B3, BIOS 2.31) |
| Touchpad | Goodix GXTP7863:00 27C6:01E0 on i2c-hid-acpi (i2c_designware.0) |
Related, but not this bug
- #3893 — different Huawei model (b3 520) and different symptom (pad only works if touched before the lock screen).
- #8565 — ELAN I2C pad on an HP, not Goodix.
- #9190 / #8376 / #9252 —
omarchy-hw-touchpadname-matching misses. When this chip does bind, the name matches; the fresh-install failure is that it often does not bind at all. - #7361 / #8255 — scroll speed / 3-finger gestures. Not “no input at all”.
View raw text
### System details Intel i7-1165G7, Intel Iris Xe, Huawei MateBook D (BOD-WXX9 / BOD-WXX9-PCB-B3, BIOS 2.31), Omarchy 4.0.1-1 (Hyprland 0.56.2, kernel 7.1.9-arch1-2) ### What's wrong? On a fresh Omarchy install, the built-in touchpad on this Huawei MateBook D produced **no pointer motion, scrolling, or taps**. The rest of the desktop came up normally; the failure was specific to the internal pad. **Cause (from the install-day journal, not from a later healthy boot):** the kernel's `i2c_hid_acpi` probe for `i2c-GXTP7863:00` fails with **`-110` (`ETIMEDOUT`)**. On those boots there is no GXTP input node at all, so Omarchy / Hyprland / libinput have nothing to configure. This is not an `omarchy-hw-touchpad` name-matching miss. **Version (from install logs, not guessed):** - ISO / installer on 2026-08-25 shipped `omarchy 4.0.0-1` (`omarchy-settings 4.0.0-1`). That matches downloading “the current ISO” before [v4.0.1](https://github.com/omacom/omarchy/releases/tag/v4.0.1) existed (v4.0.0 was 2026-08-14; v4.0.1 published 2026-08-25 11:24 UTC). - The first `pacman -Syu` the same evening upgraded `omarchy` `4.0.0-1` → `4.0.1-1` (22:38 +03). - First boot was one minute later (22:39 +03), so the first graphical session — and this machine still — is **Omarchy 4.0.1-1**. I am not claiming this was a 4.0.1 ISO. #### Steps to reproduce 1. Fresh-install Omarchy from the 4.0.0 ISO on a Huawei BOD-WXX9 (MateBook D); first boot after the installer’s online update to 4.0.1. 2. Reach the desktop / lock screen without adding user `input.lua` or libinput quirks. 3. Use the built-in touchpad: move, tap-to-click, two-finger scroll. #### Expected The internal Goodix pad works as a touchpad out of the box (move, tap, scroll). #### Actual The pad does not register those inputs. Kernel log on the failed boots: ``` i2c_hid_acpi i2c-GXTP7863:00: can't add hid device: -110 i2c_hid_acpi i2c-GXTP7863:00: probe with driver i2c_hid_acpi failed with error -110 ``` Per-boot journal (including the later successful bind) is in the comment below. #### Hardware | | | |---|---| | DMI | `HUAWEI` `BOD-WXX9` (family: MateBook D, board: `BOD-WXX9-PCB-B3`, BIOS 2.31) | | Touchpad | Goodix `GXTP7863:00 27C6:01E0` on `i2c-hid-acpi` (`i2c_designware.0`) | #### Related, but not this bug - #3893 — different Huawei model (b3 520) and different symptom (pad only works if touched before the lock screen). - #8565 — ELAN I2C pad on an HP, not Goodix. - #9190 / #8376 / #9252 — `omarchy-hw-touchpad` name-matching misses. When this chip *does* bind, the name matches; the fresh-install failure is that it often does not bind at all. - #7361 / #8255 — scroll speed / 3-finger gestures. Not “no input at all”.
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 10:15 UTC