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.
Built-in keyboard on Fujitsu LIFEBOOK P727 is unresponsive at disk unlock prompt
Reported by DWRedShoes · filed Sep 28, 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
System details
Fujitsu LIFEBOOK P727 (UEFI 1.27); Omarchy 4.0.4-1; Linux 7.2.5-3-omarchy.
What's wrong?
At early boot, the built-in keyboard does not accept input at the encrypted-root (LUKS) unlock prompt. The same keyboard works in UEFI setup and the boot menu, and works normally after Linux finishes booting. I had to use a USB keyboard to enter the disk passphrase.
The kernel detects the built-in keyboard after boot as an AT Translated Set 2 keyboard on the i8042 controller. Its boot log reports an active i8042 multiplexing controller.
Workaround confirmed
Adding i8042.nomux to the kernel command line fixed input at the unlock prompt. I first verified it as a one-boot Limine option, then persisted it with KERNEL_CMDLINE[default]+=" i8042.nomux" in /etc/limine-entry-tool.d/lifebook-p727-i8042.conf and rebuilt the UKI using limine-mkinitcpio. The built-in keyboard continued working at disk unlock after reboot.
Could this model/controller behavior be documented or otherwise handled for affected hardware? I have not attached the full diagnostic output because it includes machine-specific identifiers and network details.
View raw text
### System details Fujitsu LIFEBOOK P727 (UEFI 1.27); Omarchy 4.0.4-1; Linux 7.2.5-3-omarchy. ### What's wrong? At early boot, the built-in keyboard does not accept input at the encrypted-root (LUKS) unlock prompt. The same keyboard works in UEFI setup and the boot menu, and works normally after Linux finishes booting. I had to use a USB keyboard to enter the disk passphrase. The kernel detects the built-in keyboard after boot as an AT Translated Set 2 keyboard on the i8042 controller. Its boot log reports an active i8042 multiplexing controller. ### Workaround confirmed Adding `i8042.nomux` to the kernel command line fixed input at the unlock prompt. I first verified it as a one-boot Limine option, then persisted it with `KERNEL_CMDLINE[default]+=" i8042.nomux"` in `/etc/limine-entry-tool.d/lifebook-p727-i8042.conf` and rebuilt the UKI using `limine-mkinitcpio`. The built-in keyboard continued working at disk unlock after reboot. Could this model/controller behavior be documented or otherwise handled for affected hardware? I have not attached the full diagnostic output because it includes machine-specific identifiers and network details.
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 19:52 UTC