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.
limine-scan (documented dual-boot step) generates a Windows entry that panics at boot
Reported by alkevintan · filed Aug 23, 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
Bug description
The dual-boot manual (manual/50-dual-boot-install.md) instructs users to run limine-scan to add Windows to the Limine menu.
What happens:
limine-scan→limine-entry-tool --scanreads EFI paths fromefibootmgr, which reports Windows' path in uppercase:\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI- The scanner only converts backslashes to slashes and writes the path verbatim into
/boot/limine.conf:
/Windows Boot Manager
protocol: efi
path: guid(<esp-partuuid>):/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI- The actual files on the ESP are
EFI/Microsoft/Boot/bootmgfw.efi. Limine's own FAT driver performs case-sensitive lookups, so selecting the entry panics at boot with "image not found — is the path correct?"
Verified on my system: correcting the path casing made Windows boot immediately.
Suggested fix
Resolve each scanned EFI path against the real directory entries on the target ESP and write the exact on-disk casing (fall back to the raw string if resolution fails). Alternatively fix upstream at https://gitlab.com/Zesko/limine-entry-tool (EfiScanner.java) — happy to provide logs.
View raw text
### Bug description
The dual-boot manual ([manual/50-dual-boot-install.md](https://github.com/basecamp/omarchy/blob/main/manual/50-dual-boot-install.md)) instructs users to run `limine-scan` to add Windows to the Limine menu.
What happens:
1. `limine-scan` → `limine-entry-tool --scan` reads EFI paths from `efibootmgr`, which reports Windows' path in uppercase: `\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI`
2. The scanner only converts backslashes to slashes and writes the path verbatim into `/boot/limine.conf`:
```
/Windows Boot Manager
protocol: efi
path: guid(<esp-partuuid>):/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
```
3. The actual files on the ESP are `EFI/Microsoft/Boot/bootmgfw.efi`. Limine's own FAT driver performs **case-sensitive** lookups, so selecting the entry panics at boot with *"image not found — is the path correct?"*
Verified on my system: correcting the path casing made Windows boot immediately.
### Suggested fix
Resolve each scanned EFI path against the real directory entries on the target ESP and write the exact on-disk casing (fall back to the raw string if resolution fails). Alternatively fix upstream at https://gitlab.com/Zesko/limine-entry-tool (`EfiScanner.java`) — happy to provide logs.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 08:30 UTC