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.
Omarchy 3.4.0 breaks boot with LUKS encryption - emergency mode with locked root
Reported by folone · filed Feb 27, 2026Closed upstream on 2026-04-02 by its own reporter folone. GitHub close reason: completed. Closed by its own reporter — not by itself 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
Omarchy 3.4.0 (upgrading from 3.3.3)
What's wrong?
After upgrading to Omarchy 3.4.0, the system fails to boot and drops into emergency mode with a locked root filesystem. The boot process appears to hang at LUKS unlock, preventing access to the encrypted root partition.
Environment:
- Omarchy Version: 3.4.0 (upgrading from 3.3.3)
- Kernel: 6.18.9-arch1-2 (after upgrade), 6.18.7-arch1-1 (working)
- Disk Layout: NVMe with GPT, LUKS encryption, Btrfs subvolumes (@, @home, @pkg, @log)
- Previous Working State: Omarchy 3.3.3 with kernel 6.18.7
What fixed this for me:
* Boot from a working snapshot (this ended up being second oldest snapshot for me)
* Revert hooks to HOOKS=(base udev plymouth autodetect microcode modconf kms keyboard keymap consolefont block encrypt filesystems fsck)
* Revert linux to 6.18.7
* Rebuilding UKI with sudo mkinitcpio -p linux
Any recommendations for how to realign my system back with the upstream, and still have the working boot process?
View raw text
### System details Omarchy 3.4.0 (upgrading from 3.3.3) ### What's wrong? After upgrading to Omarchy 3.4.0, the system fails to boot and drops into emergency mode with a locked root filesystem. The boot process appears to hang at LUKS unlock, preventing access to the encrypted root partition. Environment: - Omarchy Version: 3.4.0 (upgrading from 3.3.3) - Kernel: 6.18.9-arch1-2 (after upgrade), 6.18.7-arch1-1 (working) - Disk Layout: NVMe with GPT, LUKS encryption, Btrfs subvolumes (@, @home, @pkg, @log) - Previous Working State: Omarchy 3.3.3 with kernel 6.18.7 What fixed this for me: * Boot from a working snapshot (this ended up being second oldest snapshot for me) * Revert hooks to `HOOKS=(base udev plymouth autodetect microcode modconf kms keyboard keymap consolefont block encrypt filesystems fsck)` * Revert linux to 6.18.7 * Rebuilding UKI with `sudo mkinitcpio -p linux` Any recommendations for how to realign my system back with the upstream, and still have the working boot process?
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.