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.
Installation Stopped due to full EFI Vars
Reported by hossimo · filed Oct 26, 2025Closed upstream on 2025-10-26 by ryanrhughes, as not planned.
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
Thinkstation Lenovo P3 Tiny
What's wrong?
Maybe about a month (v3.0.2) ago I tried installing Omarchy but it failed during the install and I did not have time to look into the issue, I got as far as finding out the issue had something to do with EFI vars and not being able to add an entry into NVRAM.
Today (v3.1.3) I tried again a did a little more digging
During the install everything went fine until efibootmgr tried to create a new UEFI boot entry into the system NVRAM.
I tried running the below:
root@archiso ~ # efibootmgr
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0003,0002,0001,0004,0005
Boot0001* UEFI: PXE IPv4 Intel(R) Ethernet Connection (17) I219-LM PciRoot(0x0)/Pci(0x1f,0x6)/MAC(c4c6e6f456ea,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)0000424f
Boot0002* UEFI: PXE IPv6 Intel(R) Ethernet Connection (17) I219-LM PciRoot(0x0)/Pci(0x1f,0x6)/MAC(c4c6e6f456ea,0)/IPv6([::],0,Static,[::],[::],64)0000424f
Boot0003* UEFI OS HD(1,GPT,4f5d8d5f-50d2-4266-821f-e33e74d1964f,0x800,0x100000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0004* UEFI: SanDisk, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/HD(1,MBR,0x1f7be63a,0x800,0x1ca2fa8)0000424f
Boot0005* UEFI: SanDisk, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/HD(2,MBR,0x1f7be63a,0x1ca37a8,0x800)0000424f
I tried removing all of the entries but they all failed:
15 root@archiso ~ # efibootmgr -b 0001 -B
Could not delete variable: No such file or directory
15 root@archiso ~ # efibootmgr -b 0002 -B
Could not delete variable: No space left on device
15 root@archiso ~ # efibootmgr -b 0003 -B
Could not delete variable: No space left on device
15 root@archiso ~ # efibootmgr -b 0004 -B
Could not delete variable: No space left on device
15 root@archiso ~ # efibootmgr -b 0005 -B
Could not delete variable: No space left on deviceAnd trying to manually install the entry fails due to no space left:
efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "Arch Linux" --loader /EFI/limine/BOOTX64.EFIarch and omarchy logs.
It feels like an limine issue as I just had Arch and debian both installed on this machine but with GRUB
install.log
omarchy-install.log
Edit:
I forgot to mention, Secure Boot is off,
and I just tried excluding the Network adapter PXE entries to see if that would make room, but it still failed and oddley the PXE devices were still in the list.
View raw text
### System details Thinkstation Lenovo P3 Tiny ### What's wrong? Maybe about a month (v3.0.2) ago I tried installing Omarchy but it failed during the install and I did not have time to look into the issue, I got as far as finding out the issue had something to do with EFI vars and not being able to add an entry into NVRAM. Today (v3.1.3) I tried again a did a little more digging During the install everything went fine until efibootmgr tried to create a new UEFI boot entry into the system NVRAM. I tried running the below: ``` root@archiso ~ # efibootmgr BootCurrent: 0004 Timeout: 1 seconds BootOrder: 0003,0002,0001,0004,0005 Boot0001* UEFI: PXE IPv4 Intel(R) Ethernet Connection (17) I219-LM PciRoot(0x0)/Pci(0x1f,0x6)/MAC(c4c6e6f456ea,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)0000424f Boot0002* UEFI: PXE IPv6 Intel(R) Ethernet Connection (17) I219-LM PciRoot(0x0)/Pci(0x1f,0x6)/MAC(c4c6e6f456ea,0)/IPv6([::],0,Static,[::],[::],64)0000424f Boot0003* UEFI OS HD(1,GPT,4f5d8d5f-50d2-4266-821f-e33e74d1964f,0x800,0x100000)/\EFI\BOOT\BOOTX64.EFI0000424f Boot0004* UEFI: SanDisk, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/HD(1,MBR,0x1f7be63a,0x800,0x1ca2fa8)0000424f Boot0005* UEFI: SanDisk, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/HD(2,MBR,0x1f7be63a,0x1ca37a8,0x800)0000424f ``` I tried removing all of the entries but they all failed: ``` 15 root@archiso ~ # efibootmgr -b 0001 -B Could not delete variable: No such file or directory 15 root@archiso ~ # efibootmgr -b 0002 -B Could not delete variable: No space left on device 15 root@archiso ~ # efibootmgr -b 0003 -B Could not delete variable: No space left on device 15 root@archiso ~ # efibootmgr -b 0004 -B Could not delete variable: No space left on device 15 root@archiso ~ # efibootmgr -b 0005 -B Could not delete variable: No space left on device ``` And trying to manually install the entry fails due to no space left: ``` efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "Arch Linux" --loader /EFI/limine/BOOTX64.EFI ``` arch and omarchy logs. It feels like an limine issue as I just had Arch and debian both installed on this machine but with GRUB [install.log](https://github.com/user-attachments/files/23152830/install.log) [omarchy-install.log](https://github.com/user-attachments/files/23152829/omarchy-install.log) Edit: I forgot to mention, Secure Boot is off, and I just tried excluding the Network adapter PXE entries to see if that would make room, but it still failed and oddley the PXE devices were still in the list.
- install.log
- omarchy-install.log
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.