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.
Device-specific keyboard presets to ensure LUKS/Plymouth input works on first boot (no external keyboard required)
Reported by bleevo · filed Oct 9, 2025Closed upstream on 2025-10-14 by its own reporter bleevo. 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
What do you need?
On some laptops, the internal keyboard is unavailable at the LUKS/Plymouth prompt after install, even though it works in the installer. I’m proposing device-specific initramfs presets (and an installer pre-flight check) so first boot always has a working keyboard without needing a USB keyboard.
Related: #1666, #729.
Problem
In the installer, keyboard input works (likely due to a broader set of input/HID modules and keymap handling).
After install/first boot, the initramfs often lacks the right keyboard module so the keyboard doesn’t work at the LUKS prompt.
First-time users can be locked out and may assume the system is bricked.
I resolved this post-install by adjusting /etc/mkinitcpio.conf and rebuilding, but this is non-obvious for new users.
Proposal
Ship a small catalogue of keyboard/HID module presets mapped to common laptop families. That the user can select during install.
AND/OR
Attempt to detect that this will be an issue during install and prompt the user to select from available modules.
View raw text
### What do you need? On some laptops, the internal keyboard is unavailable at the LUKS/Plymouth prompt after install, even though it works in the installer. I’m proposing device-specific initramfs presets (and an installer pre-flight check) so first boot always has a working keyboard without needing a USB keyboard. Related: #1666, #729. **Problem** In the installer, keyboard input works (likely due to a broader set of input/HID modules and keymap handling). After install/first boot, the initramfs often lacks the right keyboard module so the keyboard doesn’t work at the LUKS prompt. First-time users can be locked out and may assume the system is bricked. I resolved this post-install by adjusting /etc/mkinitcpio.conf and rebuilding, but this is non-obvious for new users. **Proposal** Ship a small catalogue of keyboard/HID module presets mapped to common laptop families. That the user can select during install. AND/OR Attempt to detect that this will be an issue during install and prompt the user to select from available modules.
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.