Proof Portal

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-4475GitHub issuePublicReceived

Boot-time systemd-stub random-seed warning under Limine

Reported by diegnghtmr · filed Jul 1, 2026Closed upstream on 2026-07-19 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

Boot-time systemd-stub random-seed warning under Liminerevision 1 · captured 2026-10-04 11:56 UTC via poll

Summary

On an Omarchy system booting with Limine and a UKI, a boot-time message appears before userspace starts:

/systemd/src/boot/random-seed.c:216@process_random_seed: Failed to open random seed file: Not found

The system boots successfully and no matching warning appears in journalctl after boot. The issue appears to happen in systemd-stub inside the UKI, not in userspace services.

Environment

  • OS: Omarchy / Arch Linux
  • Boot loader: Limine 12.3.3
  • UKI path: /boot/EFI/Linux/omarchy_linux.efi
  • ESP / boot mount: /boot
  • Filesystem: vfat
  • systemd package/stub seen in UKI strings: systemd-stub 261.1-1-arch
  • Secure Boot: disabled
  • TPM2: supported

Evidence collected

bootctl status reports:

systemd-boot not installed in ESP.
Current Boot Loader:
        Product: Limine 12.3.3
       Features: ...
                 ✗ Support for passing random seed to OS
      Partition: /dev/disk/by-partuuid/8bbff3af-a3ef-4720-94dd-d615caade743
         Loader: └─/boot/EFI/Linux/omarchy_linux.efi
  Current Entry: Omarchy/linux

bootctl --print-stub-path reports:

/boot/EFI/Linux/omarchy_linux.efi

/boot/loader/random-seed exists and is owned by root:

/boot/loader/random-seed
Size: 32
Access: (0600/-rw-------)  Uid: (0/root)  Gid: (0/root)

EFI variables include both Loader and Stub variables, including:

LoaderSystemToken-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
StubDevicePartUUID-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
StubImageIdentifier-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
StubInfo-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

Userspace random seed service is healthy:

systemd-random-seed.service - Load/Save OS Random Seed
Active: active (exited)
ExecStart=/usr/lib/systemd/systemd-random-seed load (code=exited, status=0/SUCCESS)

systemd-boot-random-seed.service was masked temporarily as a test and the message still appeared on reboot, which suggests the visible warning is not emitted by the userspace service:

Loaded: masked
Active: inactive (dead)

Related issue

This appears adjacent to, but not the same as, #5377.

#5377 covers userspace warnings like:

Mount point '/boot' which backs the random seed file is world accessible
Random seed file '/boot/loader/random-seed' is world accessible

That part was fixed locally by changing the vfat mount masks from:

fmask=0022,dmask=0022

to:

fmask=0177,dmask=0077

After remounting, /boot/loader/random-seed correctly appears as 0600, and journalctl -b -p warning --no-pager | grep -i "random\|seed\|boot\|limine\|uki" returns no output.

However, the early visual boot message still appears.

Steps to reproduce

  1. Boot Omarchy using Limine with the generated UKI at /boot/EFI/Linux/omarchy_linux.efi.
  2. Observe early boot output before userspace starts.
  3. The message appears:
/systemd/src/boot/random-seed.c:216@process_random_seed: Failed to open random seed file: Not found

Expected behavior

If Omarchy's supported boot path is Limine + UKI, boot should not show a systemd-stub random-seed warning when:

  • /boot/loader/random-seed exists,
  • LoaderSystemToken exists,
  • systemd-random-seed.service succeeds,
  • and the system is otherwise booting normally.

Alternatively, if this warning is expected/harmless with Limine, it would be useful to document it in troubleshooting guidance.

Actual behavior

A visible pre-userspace warning appears on boot, but the system boots normally and userspace logs do not show a corresponding warning after boot.

Notes

This may be a compatibility edge between:

  • Limine,
  • Omarchy UKIs using systemd-stub,
  • systemd 261 stub random-seed handling,
  • and the fact that bootctl status reports Limine does not support passing random seed to the OS.

I am not suggesting switching bootloaders. I am reporting this because Omarchy appears to use Limine by default, and the warning is confusing for users because common advice for /var/lib/systemd/random-seed does not apply here.

View raw text
## Summary

On an Omarchy system booting with Limine and a UKI, a boot-time message appears before userspace starts:

```text
/systemd/src/boot/random-seed.c:216@process_random_seed: Failed to open random seed file: Not found
```

The system boots successfully and no matching warning appears in `journalctl` after boot. The issue appears to happen in `systemd-stub` inside the UKI, not in userspace services.

## Environment

- OS: Omarchy / Arch Linux
- Boot loader: Limine 12.3.3
- UKI path: `/boot/EFI/Linux/omarchy_linux.efi`
- ESP / boot mount: `/boot`
- Filesystem: `vfat`
- systemd package/stub seen in UKI strings: `systemd-stub 261.1-1-arch`
- Secure Boot: disabled
- TPM2: supported

## Evidence collected

`bootctl status` reports:

```text
systemd-boot not installed in ESP.
Current Boot Loader:
        Product: Limine 12.3.3
       Features: ...
                 ✗ Support for passing random seed to OS
      Partition: /dev/disk/by-partuuid/8bbff3af-a3ef-4720-94dd-d615caade743
         Loader: └─/boot/EFI/Linux/omarchy_linux.efi
  Current Entry: Omarchy/linux
```

`bootctl --print-stub-path` reports:

```text
/boot/EFI/Linux/omarchy_linux.efi
```

`/boot/loader/random-seed` exists and is owned by root:

```text
/boot/loader/random-seed
Size: 32
Access: (0600/-rw-------)  Uid: (0/root)  Gid: (0/root)
```

EFI variables include both Loader and Stub variables, including:

```text
LoaderSystemToken-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
StubDevicePartUUID-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
StubImageIdentifier-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
StubInfo-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
```

Userspace random seed service is healthy:

```text
systemd-random-seed.service - Load/Save OS Random Seed
Active: active (exited)
ExecStart=/usr/lib/systemd/systemd-random-seed load (code=exited, status=0/SUCCESS)
```

`systemd-boot-random-seed.service` was masked temporarily as a test and the message still appeared on reboot, which suggests the visible warning is not emitted by the userspace service:

```text
Loaded: masked
Active: inactive (dead)
```

## Related issue

This appears adjacent to, but not the same as, #5377.

#5377 covers userspace warnings like:

```text
Mount point '/boot' which backs the random seed file is world accessible
Random seed file '/boot/loader/random-seed' is world accessible
```

That part was fixed locally by changing the vfat mount masks from:

```text
fmask=0022,dmask=0022
```

to:

```text
fmask=0177,dmask=0077
```

After remounting, `/boot/loader/random-seed` correctly appears as `0600`, and `journalctl -b -p warning --no-pager | grep -i "random\|seed\|boot\|limine\|uki"` returns no output.

However, the early visual boot message still appears.

## Steps to reproduce

1. Boot Omarchy using Limine with the generated UKI at `/boot/EFI/Linux/omarchy_linux.efi`.
2. Observe early boot output before userspace starts.
3. The message appears:

```text
/systemd/src/boot/random-seed.c:216@process_random_seed: Failed to open random seed file: Not found
```

## Expected behavior

If Omarchy's supported boot path is Limine + UKI, boot should not show a systemd-stub random-seed warning when:

- `/boot/loader/random-seed` exists,
- `LoaderSystemToken` exists,
- `systemd-random-seed.service` succeeds,
- and the system is otherwise booting normally.

Alternatively, if this warning is expected/harmless with Limine, it would be useful to document it in troubleshooting guidance.

## Actual behavior

A visible pre-userspace warning appears on boot, but the system boots normally and userspace logs do not show a corresponding warning after boot.

## Notes

This may be a compatibility edge between:

- Limine,
- Omarchy UKIs using systemd-stub,
- systemd 261 stub random-seed handling,
- and the fact that `bootctl status` reports Limine does not support passing random seed to the OS.

I am not suggesting switching bootloaders. I am reporting this because Omarchy appears to use Limine by default, and the warning is confusing for users because common advice for `/var/lib/systemd/random-seed` does not apply here.

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.