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.
ThinkPad T470 boot loop when TPM is visible but unresponsive
Reported by KalenJosifovski · filed Aug 25, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #5087 (R-1995). 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
Fresh Omarchy 4.0.0 installation from the latest ISO available on 2026-08-24, installed into free space alongside an existing encrypted Ubuntu installation.
Hardware/firmware:
- Lenovo ThinkPad T470
- BIOS: N1QET67W 1.42
- Embedded Controller: N1QHT46W 1.28
After a successful installation, Omarchy reached the graphical login screen. Entering the correct password briefly showed a loading state, then the machine rebooted to Limine. Selecting Omarchy repeated the same login -> reboot loop.
The previous boot journal showed TPM failures followed by a forced reboot:
TPM0: Operation timed out
Failed to create TPM2 context: State not recoverable
Failed to start TPM PCR Barrier (Initialization).
systemd-pcrphase-sysinit.service: Failed with result exit-code.
Forcibly rebooting: unit systemd-pcrphase-sysinit.service failedOther TPM errors included input/output errors and invalid TPM status responses.
Workaround
In UEFI/BIOS:
Security -> Security Chip -> DisabledAfter fully disabling the Security Chip/TPM, Omarchy booted normally. I did not use Clear Security Chip; Physical Presence for Clear remains enabled.
Expected behaviour
A TPM that is present but cannot respond correctly should cause TPM/PCR measurement to be skipped or degraded gracefully, rather than forcing a reboot and leaving the user in a login loop.
View raw text
Fresh Omarchy 4.0.0 installation from the latest ISO available on 2026-08-24, installed into free space alongside an existing encrypted Ubuntu installation. Hardware/firmware: - Lenovo ThinkPad T470 - BIOS: N1QET67W 1.42 - Embedded Controller: N1QHT46W 1.28 After a successful installation, Omarchy reached the graphical login screen. Entering the correct password briefly showed a loading state, then the machine rebooted to Limine. Selecting Omarchy repeated the same login -> reboot loop. The previous boot journal showed TPM failures followed by a forced reboot: ```text TPM0: Operation timed out Failed to create TPM2 context: State not recoverable Failed to start TPM PCR Barrier (Initialization). systemd-pcrphase-sysinit.service: Failed with result exit-code. Forcibly rebooting: unit systemd-pcrphase-sysinit.service failed ``` Other TPM errors included input/output errors and invalid TPM status responses. ## Workaround In UEFI/BIOS: ```text Security -> Security Chip -> Disabled ``` After fully disabling the Security Chip/TPM, Omarchy booted normally. I did not use Clear Security Chip; Physical Presence for Clear remains enabled. ## Expected behaviour A TPM that is present but cannot respond correctly should cause TPM/PCR measurement to be skipped or degraded gracefully, rather than forcing a reboot and leaving the user in a login loop.
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.