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.
USB Bootable Media Validation Fails — Missing EFI Files
Reported by kvidaxl · filed Oct 6, 2025Closed upstream on 2025-10-06 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
Acer Swift 3 (SF314-71, 16GB RAM)
What's wrong?
After creating a USB bootable media using Rufus 4.10 and booting it on my system, the built-in UEFI media validation reports 99.7%, with 96/96 files processed, and 2 failed checks.
The errors point to missing or mis-named EFI files:
.\EFI\BOOT\BOOTIA32_original.efi: [14] Not Found
.\EFI\BOOT\B0OTx64_original.efi: [14] Not FoundThe USB was created from the ISO omarchy-3.0.2.iso downloaded from https://iso.omarchy.org/omarchy-3.0.2.iso
with SHA256 checksum verified.
Tool: Rufus 4.10 OS: Windows 11 x64 Target Device: Acer Swift 3, SF314-71, 16GB RAM ISO: omarchy-3.0.2.iso Partition Scheme: GPT Target System: UEFI (Non-CSM)
Possible bug source: uefi-md5sum
Despite the failed tests, I proceeded with the installation, which was smooth and successful.
Images
<img width="300" alt="Image" src="https://github.com/user-attachments/assets/c611353b-30ca-4264-934c-522142a77696" />
<img width="300" alt="Image" src="https://github.com/user-attachments/assets/83f656a3-59aa-491a-8831-b5d83569e6e4" />
<img width="300" alt="Image" src="https://github.com/user-attachments/assets/f860f267-f72f-4c92-9b45-6d123013e6d4" />
<img width="300" alt="Image" src="https://github.com/user-attachments/assets/87532655-f297-437f-9826-caed2995abcc" />
View raw text
### System details Acer Swift 3 (SF314-71, 16GB RAM) ### What's wrong? After creating a USB bootable media using Rufus 4.10 and booting it on my system, the built-in UEFI media validation reports 99.7%, with 96/96 files processed, and 2 failed checks. The errors point to missing or mis-named EFI files: ``` .\EFI\BOOT\BOOTIA32_original.efi: [14] Not Found .\EFI\BOOT\B0OTx64_original.efi: [14] Not Found ``` The USB was created from the ISO omarchy-3.0.2.iso downloaded from https://iso.omarchy.org/omarchy-3.0.2.iso with SHA256 checksum verified. > Tool: Rufus 4.10 > OS: Windows 11 x64 > Target Device: Acer Swift 3, SF314-71, 16GB RAM > ISO: omarchy-3.0.2.iso > Partition Scheme: GPT > Target System: UEFI (Non-CSM) Possible bug source: [uefi-md5sum](https://github.com/pbatard/uefi-md5sum#:~:text=uefi%2Dmd5sum%20is,on%20each%20boot.) Despite the failed tests, I proceeded with the installation, which was smooth and successful. Images <img width="300" alt="Image" src="https://github.com/user-attachments/assets/c611353b-30ca-4264-934c-522142a77696" /> <img width="300" alt="Image" src="https://github.com/user-attachments/assets/83f656a3-59aa-491a-8831-b5d83569e6e4" /> <img width="300" alt="Image" src="https://github.com/user-attachments/assets/f860f267-f72f-4c92-9b45-6d123013e6d4" /> <img width="300" alt="Image" src="https://github.com/user-attachments/assets/87532655-f297-437f-9826-caed2995abcc" />
- c611353b-30ca-4264-934c-522142a77696
- 83f656a3-59aa-491a-8831-b5d83569e6e4
- f860f267-f72f-4c92-9b45-6d123013e6d4
- 87532655-f297-437f-9826-caed2995abcc
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.