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.
Migration from v3.1.5 to v3.1.7 causes boot failure due to inconsistent limine.conf files
Reported by ammarove · filed Nov 9, 2025Closed upstream on 2025-11-10 by ryanrhughes. 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
20VE (ThinkBook 15 G2 ITL) | Omarchy 3.1.7
What's wrong?
During the upgrade from v3.1.5 to v3.1.7, the migration process updates /boot/limine.conf but fails to update /boot/EFI/limine/limine.conf (which is the actual config file read by the bootloader). This causes the "Failed to open kernel with path 'boot():/vmlinuz-linux'" error on boot.
Root Cause:
The migration updates /boot/limine.conf with the new UKI path and hash
But /boot/EFI/limine/limine.conf still contains the old format pointing to /vmlinuz-linux
my bootloader reads /boot/EFI/limine/limine.conf, not /boot/limine.conf
Workaround:
- Booted from your second working omarchy installation (on SDA disk) | or usb bootable device
- Mounted the broken system:
sudo cryptsetup luksOpen /dev/nvme0n1p2 cryptroot_nvme
sudo mount -o subvol=@ /dev/mapper/cryptroot_nvme /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot- bash sudo cp /mnt/boot/limine.conf /mnt/boot/EFI/limine/limine.conf
- Properly unmounted and rebooted:
sudo umount -R /mnt
sudo cryptsetup luksClose cryptroot_nvme
sync
rebootView raw text
### System details 20VE (ThinkBook 15 G2 ITL) | Omarchy 3.1.7 ### What's wrong? During the upgrade from v3.1.5 to v3.1.7, the migration process updates /boot/limine.conf but fails to update /boot/EFI/limine/limine.conf (which is the actual config file read by the bootloader). This causes the "Failed to open kernel with path 'boot():/vmlinuz-linux'" error on boot. Root Cause: The migration updates /boot/limine.conf with the new UKI path and hash But /boot/EFI/limine/limine.conf still contains the old format pointing to /vmlinuz-linux my bootloader reads /boot/EFI/limine/limine.conf, not /boot/limine.conf ### Workaround: - Booted from your second working omarchy installation (on SDA disk) | or usb bootable device - Mounted the broken system: ``` sudo cryptsetup luksOpen /dev/nvme0n1p2 cryptroot_nvme sudo mount -o subvol=@ /dev/mapper/cryptroot_nvme /mnt sudo mount /dev/nvme0n1p1 /mnt/boot ``` - bash sudo cp /mnt/boot/limine.conf /mnt/boot/EFI/limine/limine.conf - Properly unmounted and rebooted: ``` sudo umount -R /mnt sudo cryptsetup luksClose cryptroot_nvme sync reboot ```
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.