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.
LUKS password prompt fails on boot after Plymouth update
Reported by Jick1164 · filed Jul 4, 2026Closed upstream on 2026-07-16 by its own reporter Jick1164. 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.8.2, 7.0.10-arch1-1, NVIDIA graphic card
What's wrong?
Hi,
This is my first time reporting a bug, and I'm a complete Linux beginner, so I hope I'm giving you the right information.
I updated my system this morning using sudo pacman -Syu. Following this update, I was unable to log into Omarchy — failing on login screen.
I heavily used Claude AI to debug this, since I don't have much Linux knowledge myself. It turned out to be the Plymouth update that broke my system. Downgrading Plymouth to 24.004.60-14 (from the pacman cache) fixed the issue for me.
Omarchy version: 3.8.1
Plymouth versions involved: 24.004.60-14 → 26.134.222-2
Date of update: July 4, 2026
In Claude's words (I don't fully understand the technical details myself, but I hope it helps):
The Plymouth 24.x → 26.x jump appears to break the LUKS passphrase prompt display/input specifically in quiet splash boot mode on this Limine+UKI+encrypted-Btrfs setup. No initramfs generation errors were observed (limine-mkinitcpio completes successfully both before and after), so the initramfs itself isn't corrupted — the issue is specifically the Plymouth password prompt not functioning correctly at boot time.
Let me know if you need any more information — happy to help however I can.
View raw text
### System details Omarchy 3.8.2, 7.0.10-arch1-1, NVIDIA graphic card ### What's wrong? Hi, This is my first time reporting a bug, and I'm a complete Linux beginner, so I hope I'm giving you the right information. I updated my system this morning using sudo pacman -Syu. Following this update, I was unable to log into Omarchy — failing on login screen. I heavily used Claude AI to debug this, since I don't have much Linux knowledge myself. It turned out to be the Plymouth update that broke my system. Downgrading Plymouth to 24.004.60-14 (from the pacman cache) fixed the issue for me. Omarchy version: 3.8.1 Plymouth versions involved: 24.004.60-14 → 26.134.222-2 Date of update: July 4, 2026 In Claude's words (I don't fully understand the technical details myself, but I hope it helps): The Plymouth 24.x → 26.x jump appears to break the LUKS passphrase prompt display/input specifically in quiet splash boot mode on this Limine+UKI+encrypted-Btrfs setup. No initramfs generation errors were observed (limine-mkinitcpio completes successfully both before and after), so the initramfs itself isn't corrupted — the issue is specifically the Plymouth password prompt not functioning correctly at boot time. Let me know if you need any more information — happy to help however I can.
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.