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

Machine unbootable. No Limine config. No kernel entry. Nothing

Reported by endafk · filed Apr 16, 2026Closed upstream on 2026-04-17 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

Machine unbootable. No Limine config. No kernel entry. Nothingrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Lenovo ThinkPad t480, /dev/sda, Intel CPU, Omarchy 3.5 offline ISO

What's wrong?

Exact failure chain:
1. archinstall runs, gets to bootloader step
2. Crashes with:
IsADirectoryError: [Errno 21] Is a directory: '/mnt/boot/EFI/BOOT'
DiskError: Failed to install Limine in /mnt/boot

  1. archinstall then tries to copy its own log to itself and dies with a second unrelated error:

OSError: [Errno 22] Source and target are the same path:
'/var/log/archinstall/install.log' -> '/var/log/archinstall/install.log'

  1. omarchy reports Failed script: install_base_system and exits
  2. Machine is now unbootable. No Limine config. No kernel entry. Nothing.

Root cause:
archinstall’s Limine integration tries to write a file to /mnt/boot/EFI/BOOT which already exists as a directory (as it should per the UEFI spec).

What should happen:
Either the installer handles this gracefully and completes anyway, OR it fails with a clear recovery path shown on screen. Instead it just dies and leaves users with an unbootable machine and no instructions.

I have no logs, it’s late night and filed it on phone

View raw text
### System details

Lenovo ThinkPad t480, /dev/sda, Intel CPU, Omarchy 3.5 offline ISO

### What's wrong?

Exact failure chain:
	1.	archinstall runs, gets to bootloader step
	2.	Crashes with:
IsADirectoryError: [Errno 21] Is a directory: '/mnt/boot/EFI/BOOT'
DiskError: Failed to install Limine in /mnt/boot

3.	archinstall then tries to copy its own log to itself and dies with a second unrelated error:
OSError: [Errno 22] Source and target are the same path:
'/var/log/archinstall/install.log' -> '/var/log/archinstall/install.log'

4.	omarchy reports Failed script: install_base_system and exits
	5.	Machine is now unbootable. No Limine config. No kernel entry. Nothing.
Root cause:
archinstall’s Limine integration tries to write a file to /mnt/boot/EFI/BOOT which already exists as a directory (as it should per the UEFI spec).

What should happen:
Either the installer handles this gracefully and completes anyway, OR it fails with a clear recovery path shown on screen. Instead it just dies and leaves users with an unbootable machine and no instructions.

I have no logs, it’s late night and filed it on phone

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.