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.
Installer incorrectly detects non-UEFI boot when using Ventoy (UEFI confirmed)
Reported by Satbir6 · filed Apr 21, 2026Closed upstream on 2026-04-22. 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
Device: Lenovo (PN: 82Y9009KIN) Serial Number: MP2KDFWL BIOS Version: M3CN46WW Firmware Settings: Secure Boot: Disabled Boot Mode: UEFI CSM: Disabled (or not exposed) ISO: omarchy-3.5.1-2 Boot Method: Ventoy (latest) USB Boot Entry Used: UEFI: SanDisk / Ventoy
What's wrong?
The installer shows:
"Not booted with EFI or running in a container"
However, the system is actually booted in UEFI mode.
Verification
From the live environment:
ls /sys/firmware/efi
Result: Directory exists and contains files (confirms UEFI boot)
Optional additional check:
mount | grep efivars
Expected behaviour
Installer should:
Detect UEFI environment correctly
Proceed with installation without blocking
Actual behaviour
Installer incorrectly assumes:
Legacy boot mode OR
Container environment
Installation is blocked
Steps to reproduce
Create bootable USB using Ventoy
Copy omarchy-3.5.1-2.iso
Boot using:
UEFI: SanDisk / Ventoy
Launch installer
Observe EFI detection error
Additional notes
Disk was fully wiped prior to install:
diskpart
select disk 1
clean
convert gpt
No pre-existing partitions
Issue persists across reboots
Suspected cause
Incorrect EFI detection logic in installer
Possible incompatibility with:
Ventoy boot method
Limine bootloader environment
Workarounds tried
Verified UEFI boot manually → confirmed correct
Recreated USB
Ensured correct boot entry selection
View raw text
### System details Device: Lenovo (PN: 82Y9009KIN) Serial Number: MP2KDFWL BIOS Version: M3CN46WW Firmware Settings: Secure Boot: Disabled Boot Mode: UEFI CSM: Disabled (or not exposed) ISO: omarchy-3.5.1-2 Boot Method: Ventoy (latest) USB Boot Entry Used: UEFI: SanDisk / Ventoy ### What's wrong? The installer shows: "Not booted with EFI or running in a container" However, the system is actually booted in UEFI mode. Verification From the live environment: ls /sys/firmware/efi Result: Directory exists and contains files (confirms UEFI boot) Optional additional check: mount | grep efivars Expected behaviour Installer should: Detect UEFI environment correctly Proceed with installation without blocking Actual behaviour Installer incorrectly assumes: Legacy boot mode OR Container environment Installation is blocked Steps to reproduce Create bootable USB using Ventoy Copy omarchy-3.5.1-2.iso Boot using: UEFI: SanDisk / Ventoy Launch installer Observe EFI detection error Additional notes Disk was fully wiped prior to install: diskpart select disk 1 clean convert gpt No pre-existing partitions Issue persists across reboots Suspected cause Incorrect EFI detection logic in installer Possible incompatibility with: Ventoy boot method Limine bootloader environment Workarounds tried Verified UEFI boot manually → confirmed correct Recreated USB Ensured correct boot entry selection
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.