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.
ASUS Zenbook UM3406KA touchpad stops responding after s2idle resume
Reported by ottosilva · filed Sep 9, 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
ASUS Zenbook 14 UM3406KA, AMD Radeon 840M, Omarchy 4.0.3-1, Linux 7.2.3-arch1-3, BIOS UM3406KA.304
What's wrong?
The built-in ASUP1206 I2C touchpad stops responding after resuming from s2idle suspend. The device remains present and bound to i2c_hid_acpi, but the kernel reports a failed power-state restore:
i2c_hid_acpi i2c-ASUP1206:00: failed to change power setting.
PM: dpm_run_callback(): acpi_subsys_resume returns -121
i2c_hid_acpi i2c-ASUP1206:00: PM: failed to resume async: error -121The touchpad was working normally before suspend. After resume, Hyprland still lists the device, but it produces no pointer input. Rebinding only the affected HID device restores it without rebooting:
echo i2c-ASUP1206:00 | sudo tee /sys/bus/i2c/drivers/i2c_hid_acpi/unbind
echo i2c-ASUP1206:00 | sudo tee /sys/bus/i2c/drivers/i2c_hid_acpi/bindA tested workaround is to run that unbind/bind sequence from a systemd sleep hook during post resume, scoped only to i2c-ASUP1206:00. It leaves the ELAN9008 touchscreen untouched.
On this machine, the workaround has been tested after repeated suspend/resume cycles and restores the touchpad automatically. Before applying the workaround, a full power-controller reset (shutdown, then holding the power button for about 40 seconds before powering on) was required to recover the device.
This appears to be device-specific, but the same i2c_hid_acpi resume failure may affect other I2C HID touchpads.
View raw text
### System details ASUS Zenbook 14 UM3406KA, AMD Radeon 840M, Omarchy 4.0.3-1, Linux 7.2.3-arch1-3, BIOS UM3406KA.304 ### What's wrong? The built-in ASUP1206 I2C touchpad stops responding after resuming from `s2idle` suspend. The device remains present and bound to `i2c_hid_acpi`, but the kernel reports a failed power-state restore: ``` i2c_hid_acpi i2c-ASUP1206:00: failed to change power setting. PM: dpm_run_callback(): acpi_subsys_resume returns -121 i2c_hid_acpi i2c-ASUP1206:00: PM: failed to resume async: error -121 ``` The touchpad was working normally before suspend. After resume, Hyprland still lists the device, but it produces no pointer input. Rebinding only the affected HID device restores it without rebooting: ``` echo i2c-ASUP1206:00 | sudo tee /sys/bus/i2c/drivers/i2c_hid_acpi/unbind echo i2c-ASUP1206:00 | sudo tee /sys/bus/i2c/drivers/i2c_hid_acpi/bind ``` A tested workaround is to run that unbind/bind sequence from a `systemd` sleep hook during `post` resume, scoped only to `i2c-ASUP1206:00`. It leaves the ELAN9008 touchscreen untouched. On this machine, the workaround has been tested after repeated suspend/resume cycles and restores the touchpad automatically. Before applying the workaround, a full power-controller reset (shutdown, then holding the power button for about 40 seconds before powering on) was required to recover the device. This appears to be device-specific, but the same `i2c_hid_acpi` resume failure may affect other I2C HID touchpads.
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 11:18 UTC