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.
Total freeze with dead keyboard/touchpad during REAPER + yabridge/wine project loads (Lenovo Yoga Slim 7 14ILL10); earlier events also show USB4/Thunderbolt runtime-resume timeouts and an ACPI-EC global-lock livelock
Reported by thakurious · filed Sep 19, 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
What happened
On linux-omarchy 7.2.5-3 this machine periodically becomes completely unusable: no keyboard, no touchpad, no mouse, nothing reacts, and only a forced power-off recovers. The kernel log shows the ACPI-EC global lock getting stuck behind a timed-out USB4/Type-C transaction. Every occurrence is on 7.2.5-3-omarchy; the stock Arch kernel on the same machine has never done it.
Boot correlation (retained journal, Aug 28 – Sep 19)
| kernel | boots | thunderbolt ... timeout ... config space | forced reboots | REAPER sessions |
|---|---|---|---|---|
| 7.1.9-arch1-2 | 13 | 0 | 0 | 1 |
| 7.2.3-arch1-3 | 5 | 0 | 0 | 1 |
| 7.2.5-3-omarchy | 3 | 2, 1, 4 | 2 | 3 |
linux-omarchy 7.2.5-3 was installed 2026-09-16 20:38 by the 4.0.4 upgrade; the first boot on it (20:43) is the first boot in the journal with any Thunderbolt failure, and both forced reboots are on it.
Freeze 1 — 2026-09-19 (forced power-off)
10:42:18 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0xaf
10:42:39 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0x3a
10:42:39 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0x39
10:42:39 WARNING: drivers/thunderbolt/ctl.c:232 at check_config_address+0x84/0xb0 [thunderbolt],
... tb_switch_resume -> tb_switch_tmu_init -> tb_port_find_cap -> tb_cfg_read
10:43:01 thunderbolt 0000:00:0d.2: 0: timeout writing config space 1 to 0xaf
10:44:01 ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-110)
10:46:30 INFO: task systemd:1 blocked for more than 122 seconds.
10:46:30 INFO: task kworker/3:1:387101 blocked for more than 122 seconds.
... 10 hung tasks in total, all blocked the same way:
acpi_ec_event_processor -> acpi_evaluate_object -> acpi_ev_acquire_global_lock
-> acpi_ex_acquire_global_lock -> acpi_os_wait_semaphore -> down_timeout
e.g. "is blocked on a semaphore likely last held by task kworker/7:4:1332158",
where that kworker is itself stuck in acpi_ec_event_processor.
10:46:30 Future hung task reports are suppressed, see sysctl kernel.hung_task_warningsThe journal — including the shell's periodic idle-timer messages, so userspace was still scheduling — continues until 10:47:41 and then stops with no shutdown sequence at all: a forced reset. No OOM (30 GiB RAM / 61 GiB swap, 0 B swap used), no panic, no GPU hang, no storage errors.
Freeze 2 — 2026-09-17
Sep 17 21:13:15 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0xa
Sep 17 21:13:36 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0xaf
Sep 17 21:14:27 systemd-logind: Power key pressed short. <- last line of the boot; no clean shutdownWhy there is no way out of it
The internal keyboard is AT Translated Set 2 keyboard on isa0060/serio0 (i8042, EC-emulated on Lenovo) and the touchpad is ACPI i2c-HID (i2c-SYNA2BA6:00). Both are serviced through the same ACPI/EC path that wedges, so keyboard and touchpad die together — and SysRq goes through the same path, so REISUB is unavailable too. With systemd PID 1 itself blocked, nothing in the session can recover.
Suspected trigger
An external SanDisk Extreme 55DD SSD (10 Gbps UAS, NTFS via ntfs3, mounted from fstab) sits on the same USB4 host — bus 2 = 0000:00:0d.0, while the failing controller is 0000:00:0d.2 — and holds the sample libraries used in those sessions. The drive itself is healthy: zero uas/SCSI/I/O error/reset messages in the entire journal. In the 09-19 event the failing runtime resume was provoked by nvidia-modprobe reading PCI config space; note nvidia-utils is installed here (as a dependency of hyprland/steam/umu-launcher) even though this machine has no NVIDIA GPU. Runtime PM of the NHI is power/control=auto with autosuspend_delay_ms=15000, i.e. the failing path is a runtime resume out of D3.
Driver differences between the two kernels
thunderbolt.ko 7.2.3-arch1-3: srcversion FEAF8B73A96B00F9FEFEEE6
thunderbolt.ko 7.2.5-3-omarchy: srcversion 818021460DA57E63C550EC2 <- changed
typec_ucsi.ko 7.2.3: AAEE04A4788675D390B72D7 | 7.2.5: B15234902F8E9C018F85E15 <- changed
ucsi_acpi.ko identical in bothThe same USB-C/PD subsystem also reports far more change events on this kernel: power_supply change uevents (counted via the udev rule that fires on them) were 26 / 84 / 598 per boot on 7.2.3, versus 2433 / 3395 per boot on 7.2.5-3.
System
- omarchy version: 4.0.4-1
linux-omarchy 7.2.5-3(failing) vslinux 7.2.3-arch1-3(fine)- Lenovo Yoga Slim 7 14ILL10, Intel Core Ultra 200V (Lunar Lake), BIOS QSCN34WW (2026-02-06)
omarchy debugis not a command in 4.0.4-1, so no debug bundle is attached- Next step on my side: boot the stock 7.2.3 UKI from Limine and confirm zero Thunderbolt timeouts over an equivalent session
Related
Same kernel switch, adjacent subsystems: #12181 (PS/2 touchpad vanishes), #12188 (backlight / USB audio), #12187 (hard freeze with dead input), #12083, #12145.
Filed by DeepSeek v4.1 Flash (deepseek-v4.1-flash) via Pi 0.85.1.
View raw text
### What happened
On `linux-omarchy 7.2.5-3` this machine periodically becomes completely unusable: no keyboard, no touchpad, no mouse, nothing reacts, and only a forced power-off recovers. The kernel log shows the ACPI-EC global lock getting stuck behind a timed-out USB4/Type-C transaction. Every occurrence is on `7.2.5-3-omarchy`; the stock Arch kernel on the same machine has never done it.
### Boot correlation (retained journal, Aug 28 – Sep 19)
| kernel | boots | `thunderbolt ... timeout ... config space` | forced reboots | REAPER sessions |
|---|---|---|---|---|
| 7.1.9-arch1-2 | 13 | 0 | 0 | 1 |
| 7.2.3-arch1-3 | 5 | 0 | 0 | 1 |
| 7.2.5-3-omarchy | 3 | 2, 1, 4 | **2** | 3 |
`linux-omarchy 7.2.5-3` was installed 2026-09-16 20:38 by the 4.0.4 upgrade; the first boot on it (20:43) is the first boot in the journal with any Thunderbolt failure, and both forced reboots are on it.
### Freeze 1 — 2026-09-19 (forced power-off)
```
10:42:18 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0xaf
10:42:39 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0x3a
10:42:39 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0x39
10:42:39 WARNING: drivers/thunderbolt/ctl.c:232 at check_config_address+0x84/0xb0 [thunderbolt],
... tb_switch_resume -> tb_switch_tmu_init -> tb_port_find_cap -> tb_cfg_read
10:43:01 thunderbolt 0000:00:0d.2: 0: timeout writing config space 1 to 0xaf
10:44:01 ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-110)
10:46:30 INFO: task systemd:1 blocked for more than 122 seconds.
10:46:30 INFO: task kworker/3:1:387101 blocked for more than 122 seconds.
... 10 hung tasks in total, all blocked the same way:
acpi_ec_event_processor -> acpi_evaluate_object -> acpi_ev_acquire_global_lock
-> acpi_ex_acquire_global_lock -> acpi_os_wait_semaphore -> down_timeout
e.g. "is blocked on a semaphore likely last held by task kworker/7:4:1332158",
where that kworker is itself stuck in acpi_ec_event_processor.
10:46:30 Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
```
The journal — including the shell's periodic idle-timer messages, so userspace was still scheduling — continues until 10:47:41 and then stops with **no shutdown sequence at all**: a forced reset. No OOM (30 GiB RAM / 61 GiB swap, 0 B swap used), no panic, no GPU hang, no storage errors.
### Freeze 2 — 2026-09-17
```
Sep 17 21:13:15 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0xa
Sep 17 21:13:36 thunderbolt 0000:00:0d.2: 0: timeout reading config space 1 from 0xaf
Sep 17 21:14:27 systemd-logind: Power key pressed short. <- last line of the boot; no clean shutdown
```
### Why there is no way out of it
The internal keyboard is `AT Translated Set 2 keyboard` on `isa0060/serio0` (i8042, EC-emulated on Lenovo) and the touchpad is ACPI i2c-HID (`i2c-SYNA2BA6:00`). Both are serviced through the same ACPI/EC path that wedges, so keyboard and touchpad die together — and SysRq goes through the same path, so REISUB is unavailable too. With `systemd` PID 1 itself blocked, nothing in the session can recover.
### Suspected trigger
An external SanDisk Extreme 55DD SSD (10 Gbps UAS, NTFS via ntfs3, mounted from fstab) sits on the same USB4 host — bus 2 = `0000:00:0d.0`, while the failing controller is `0000:00:0d.2` — and holds the sample libraries used in those sessions. The drive itself is healthy: zero `uas`/SCSI/`I/O error`/reset messages in the entire journal. In the 09-19 event the failing runtime resume was provoked by `nvidia-modprobe` reading PCI config space; note `nvidia-utils` is installed here (as a dependency of hyprland/steam/umu-launcher) even though this machine has no NVIDIA GPU. Runtime PM of the NHI is `power/control=auto` with `autosuspend_delay_ms=15000`, i.e. the failing path is a runtime *resume* out of D3.
### Driver differences between the two kernels
```
thunderbolt.ko 7.2.3-arch1-3: srcversion FEAF8B73A96B00F9FEFEEE6
thunderbolt.ko 7.2.5-3-omarchy: srcversion 818021460DA57E63C550EC2 <- changed
typec_ucsi.ko 7.2.3: AAEE04A4788675D390B72D7 | 7.2.5: B15234902F8E9C018F85E15 <- changed
ucsi_acpi.ko identical in both
```
The same USB-C/PD subsystem also reports far more change events on this kernel: `power_supply` `change` uevents (counted via the udev rule that fires on them) were 26 / 84 / 598 per boot on 7.2.3, versus 2433 / 3395 per boot on 7.2.5-3.
### System
- omarchy version: 4.0.4-1
- `linux-omarchy 7.2.5-3` (failing) vs `linux 7.2.3-arch1-3` (fine)
- Lenovo Yoga Slim 7 14ILL10, Intel Core Ultra 200V (Lunar Lake), BIOS QSCN34WW (2026-02-06)
- `omarchy debug` is not a command in 4.0.4-1, so no debug bundle is attached
- Next step on my side: boot the stock 7.2.3 UKI from Limine and confirm zero Thunderbolt timeouts over an equivalent session
### Related
Same kernel switch, adjacent subsystems: #12181 (PS/2 touchpad vanishes), #12188 (backlight / USB audio), #12187 (hard freeze with dead input), #12083, #12145.
---
Filed by DeepSeek v4.1 Flash (`deepseek-v4.1-flash`) via Pi 0.85.1.
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 15:48 UTC