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.
linux-omarchy 7.2.5-3 boots to emergency shell on MacBookAir6,1
Reported by nordbergmikael · filed Sep 16, 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
Summary
linux-omarchy 7.2.5-3 cannot boot this encrypted MacBook Air installation. Both the normal and fallback entries enter the emergency shell. The regular Arch linux kernel boots the same installation immediately, using the same root filesystem and kernel command line.
Steps to reproduce
- Run an Omarchy update / install
linux-omarchy7.2.5-3. - In Limine, select
linux-omarchy(the configured default on this machine). - The system reaches the emergency shell.
- Select the
linux-omarchyfallback entry: it fails in the same way. - Select the regular
linuxentry: it boots normally.
Expected behavior
Both the normal and fallback linux-omarchy entries should unlock and mount the root filesystem and boot normally.
Actual behavior
Both linux-omarchy entries fail before the installed system starts and enter the emergency shell. The generic linux entry is a working workaround.
System details
- Omarchy:
4.0.4-1 - Working kernel:
linux 7.2.3.arch1-3(currently booted) - Failing kernel:
linux-omarchy 7.2.5-3 limine 12.8.0-1limine-mkinitcpio-hook 1.38.0-1.1mkinitcpio 41.1-1- Machine: Apple MacBookAir6,1
- CPU: Intel Core i5-4250U
- Root storage controller: Toshiba
1179:010b, usingahci - Root filesystem: LUKS -> Btrfs
The working kernel uses this command line, which is also configured for the Omarchy UKI:
cryptdevice=PARTUUID=35f3b70b-e128-4a0a-ad38-32b8aeb08268:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs/etc/mkinitcpio.conf is shared by both kernel images. Its hooks are:
HOOKS=(base systemd autodetect microcode modconf kms keyboard sd-vconsole block filesystems fsck)The generic kernel has successfully booted repeatedly with this setup, including after installing linux-omarchy. This makes the failure appear specific to linux-omarchy 7.2.5-3 rather than the LUKS/Btrfs configuration.
No photo from the emergency shell is attached yet because the failure occurs on the physical boot console.
View raw text
## Summary `linux-omarchy` 7.2.5-3 cannot boot this encrypted MacBook Air installation. Both the normal and fallback entries enter the emergency shell. The regular Arch `linux` kernel boots the same installation immediately, using the same root filesystem and kernel command line. ## Steps to reproduce 1. Run an Omarchy update / install `linux-omarchy` 7.2.5-3. 2. In Limine, select `linux-omarchy` (the configured default on this machine). 3. The system reaches the emergency shell. 4. Select the `linux-omarchy` fallback entry: it fails in the same way. 5. Select the regular `linux` entry: it boots normally. ## Expected behavior Both the normal and fallback `linux-omarchy` entries should unlock and mount the root filesystem and boot normally. ## Actual behavior Both `linux-omarchy` entries fail before the installed system starts and enter the emergency shell. The generic `linux` entry is a working workaround. ## System details - Omarchy: `4.0.4-1` - Working kernel: `linux 7.2.3.arch1-3` (currently booted) - Failing kernel: `linux-omarchy 7.2.5-3` - `limine 12.8.0-1` - `limine-mkinitcpio-hook 1.38.0-1.1` - `mkinitcpio 41.1-1` - Machine: Apple MacBookAir6,1 - CPU: Intel Core i5-4250U - Root storage controller: Toshiba `1179:010b`, using `ahci` - Root filesystem: LUKS -> Btrfs The working kernel uses this command line, which is also configured for the Omarchy UKI: ``` cryptdevice=PARTUUID=35f3b70b-e128-4a0a-ad38-32b8aeb08268:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs ``` `/etc/mkinitcpio.conf` is shared by both kernel images. Its hooks are: ``` HOOKS=(base systemd autodetect microcode modconf kms keyboard sd-vconsole block filesystems fsck) ``` The generic kernel has successfully booted repeatedly with this setup, including after installing `linux-omarchy`. This makes the failure appear specific to `linux-omarchy` 7.2.5-3 rather than the LUKS/Btrfs configuration. No photo from the emergency shell is attached yet because the failure occurs on the physical boot console.
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 14:10 UTC