Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-2069GitHub issuePublicDecided· Out of scope

Slow boot on systems without TPM hardware (90 second delay)

Reported by sanity · filed Oct 20, 2025 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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

Slow boot on systems without TPM hardware (90 second delay)revision 1 · captured 2026-09-28 21:29 UTC via poll

Issue

After installing Omarchy, I noticed boot time was around 2 minutes 39 seconds, which seemed excessive. After investigating with systemd-analyze and journalctl, I found that tpm2.target was waiting approximately 90 seconds for TPM devices (/dev/tpm0 and /dev/tpmrm0) that don't exist on my system.

Investigation

$ systemd-analyze
Startup finished in 31.682s (firmware) + 10.343s (loader) + 24.951s (kernel) + 1min 32.415s (userspace) = 2min 39.393s

The delay occurred between "Local File Systems" and "Trusted Platform Module" targets:

Oct 19 19:29:19 - Reached target Local File Systems
Oct 19 19:30:28 - Reached target Trusted Platform Module (TPM)

Checking for TPM devices:

$ ls -la /dev/tpm*
ls: cannot access '/dev/tpm*': No such file or directory

The system has no TPM hardware, but systemd waits for the default 90-second timeout before continuing.

Solution

Masking tpm2.target resolved the issue:

$ sudo systemctl mask tpm2.target

This should reduce boot time to approximately 1 minute or less.

Suggestion

Since many desktop systems (especially older/gaming motherboards) don't have TPM hardware, Omarchy could improve out-of-box boot performance by either:

  1. Auto-detect during installation: Check for TPM devices and automatically mask tpm2.target if none are found
  2. Ship with it masked by default: Users with actual TPM chips who need the functionality could unmask it manually

This is actually an upstream systemd/Arch issue (see systemd#33077 and Arch forums), but Omarchy could proactively handle it for better user experience.

System Info

  • Fresh Omarchy installation
  • Desktop system without TPM hardware
  • LUKS-encrypted root partition
  • Boot time improved from 2min 39sec to expected ~1min after applying fix
View raw text
## Issue

After installing Omarchy, I noticed boot time was around 2 minutes 39 seconds, which seemed excessive. After investigating with `systemd-analyze` and `journalctl`, I found that `tpm2.target` was waiting approximately 90 seconds for TPM devices (`/dev/tpm0` and `/dev/tpmrm0`) that don't exist on my system.

## Investigation

```bash
$ systemd-analyze
Startup finished in 31.682s (firmware) + 10.343s (loader) + 24.951s (kernel) + 1min 32.415s (userspace) = 2min 39.393s
```

The delay occurred between "Local File Systems" and "Trusted Platform Module" targets:
```
Oct 19 19:29:19 - Reached target Local File Systems
Oct 19 19:30:28 - Reached target Trusted Platform Module (TPM)
```

Checking for TPM devices:
```bash
$ ls -la /dev/tpm*
ls: cannot access '/dev/tpm*': No such file or directory
```

The system has no TPM hardware, but systemd waits for the default 90-second timeout before continuing.

## Solution

Masking `tpm2.target` resolved the issue:
```bash
$ sudo systemctl mask tpm2.target
```

This should reduce boot time to approximately 1 minute or less.

## Suggestion

Since many desktop systems (especially older/gaming motherboards) don't have TPM hardware, Omarchy could improve out-of-box boot performance by either:

1. **Auto-detect during installation**: Check for TPM devices and automatically mask `tpm2.target` if none are found
2. **Ship with it masked by default**: Users with actual TPM chips who need the functionality could unmask it manually

This is actually an upstream systemd/Arch issue (see [systemd#33077](https://github.com/systemd/systemd/issues/33077) and [Arch forums](https://bbs.archlinux.org/viewtopic.php?id=296699)), but Omarchy could proactively handle it for better user experience.

## System Info

- Fresh Omarchy installation
- Desktop system without TPM hardware
- LUKS-encrypted root partition
- Boot time improved from 2min 39sec to expected ~1min after applying fix

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-08 23:53 UTC