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-mkinitcpio-install calls limine-entry-tool --get-cmdline with wrong argument count, silently dropping root= from UKI cmdline
Reported by ThomsV897 · filed Sep 2, 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
Description
After a kernel/limine update, the generated /boot/limine.conf entry for the main linux kernel is missing root=, rootflags=, and rootfstype= in its cmdline: line, causing the system to boot into an emergency shell with "Failed to mount '' on real root".
Root cause found
/usr/share/libalpm/scripts/limine-mkinitcpio-install calls:
limine-entry-tool --get-cmdline "$kernel_name" --no-mutex --no-hooks | tail -n 1 >"$cmdline_file"
This passes only one positional argument ($kernel_name) to --get-cmdline.
However, the current limine-entry-tool binary (v1.37.1, from limine-mkinitcpio-hook 1.37.1-1) requires two positional arguments per its own --help:
--get-cmdline <kernel name> <profile name>
Calling it with only one argument doesn't error out loudly — it silently returns an incomplete cmdline (missing root= and related parameters), which then gets baked into the UKI, breaking boot.
Additional finding
Manually calling limine-entry-tool --get-cmdline <kernel> <profile> with a second argument (tried default, fallback) also fails with "Invalid arguments", printing the full usage block. This suggests the issue may go beyond a simple missing-argument count — the expected <profile name> value itself may differ from what's used elsewhere in Omarchy's own config (e.g. KERNEL_CMDLINE[default] in /etc/default/limine), or there may be an additional validation issue in the binary. We were unable to determine a <profile name> value that the binary accepts.
Steps to reproduce
- On a fresh Omarchy install with Btrfs + Limine
- Trigger a UKI rebuild (sudo mkinitcpio -P or a kernel update)
- Check /boot/limine.conf for the main linux entry's cmdline: line — root= is missing
- Confirm manually: limine-entry-tool --get-cmdline linux --no-mutex --no-hooks returns a cmdline without root=
Versions
- limine 12.6.0-1
- limine-mkinitcpio-hook 1.37.1-1
Workaround used
Manually editing /boot/limine.conf line to include root=PARTUUID=... rootflags=subvol=@ rw rootfstype=btrfs, plus a systemd .path unit watching the file for automatic re-patching after future regenerations.
View raw text
## Description
After a kernel/limine update, the generated /boot/limine.conf entry for the main linux kernel is missing root=, rootflags=, and rootfstype= in its cmdline: line, causing the system to boot into an emergency shell with "Failed to mount '' on real root".
## Root cause found
/usr/share/libalpm/scripts/limine-mkinitcpio-install calls:
limine-entry-tool --get-cmdline "$kernel_name" --no-mutex --no-hooks | tail -n 1 >"$cmdline_file"
This passes only one positional argument ($kernel_name) to --get-cmdline.
However, the current limine-entry-tool binary (v1.37.1, from limine-mkinitcpio-hook 1.37.1-1) requires two positional arguments per its own --help:
--get-cmdline <kernel name> <profile name>
Calling it with only one argument doesn't error out loudly — it silently returns an incomplete cmdline (missing root= and related parameters), which then gets baked into the UKI, breaking boot.
## Additional finding
Manually calling limine-entry-tool --get-cmdline <kernel> <profile> with a second argument (tried default, fallback) also fails with "Invalid arguments", printing the full usage block. This suggests the issue may go beyond a simple missing-argument count — the expected <profile name> value itself may differ from what's used elsewhere in Omarchy's own config (e.g. KERNEL_CMDLINE[default] in /etc/default/limine), or there may be an additional validation issue in the binary. We were unable to determine a <profile name> value that the binary accepts.
## Steps to reproduce
1. On a fresh Omarchy install with Btrfs + Limine
2. Trigger a UKI rebuild (sudo mkinitcpio -P or a kernel update)
3. Check /boot/limine.conf for the main linux entry's cmdline: line — root= is missing
4. Confirm manually: limine-entry-tool --get-cmdline linux --no-mutex --no-hooks returns a cmdline without root=
## Versions
- limine 12.6.0-1
- limine-mkinitcpio-hook 1.37.1-1
## Workaround used
Manually editing /boot/limine.conf line to include root=PARTUUID=... rootflags=subvol=@ rw rootfstype=btrfs, plus a systemd .path unit watching the file for automatic re-patching after future regenerations.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 10:35 UTC