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 USB Keyfile Parameter Lost During System Update
Reported by syabro · filed Sep 27, 2025Closed upstream on 2025-09-27 by ryanrhughes. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not 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 v3.0.1
What's wrong?
After pacman -Syu on 2025-09-27, my USB LUKS keyfile stopped working. System now prompts for passphrase instead of using the keyfile.
System update regenerated bootloader config and stripped the cryptkey parameter.
Working (from snapshot 2025-09-24):
kernel_cmdline: quiet splash cryptdevice=PARTUUID=f278d7fb-7688-48e7-97eb-6de149f36519:root cryptkey=UUID=5d5a6d31-93ca-4c9b-85d1-c7ae79127b1d:ext4:ssd512.key root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=/@/.snapshots/2/snapshot rw rootfstype=btrfsBroken (current):
kernel_cmdline: quiet splash cryptdevice=PARTUUID=f278d7fb-7688-48e7-97eb-6de149f36519:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfsMissing parameter: cryptkey=UUID=5d5a6d31-93ca-4c9b-85d1-c7ae79127b1d:ext4:ssd512.key
/boot/limine.conf modified at exactly update time: Sep 27 14:23
Probably bootloader config generation should preserve custom cryptkey parameters during updates somehow...
View raw text
### System details Omarchy v3.0.1 ### What's wrong? After `pacman -Syu` on 2025-09-27, my USB LUKS keyfile stopped working. System now prompts for passphrase instead of using the keyfile. System update regenerated bootloader config and stripped the `cryptkey` parameter. Working (from snapshot 2025-09-24): ``` kernel_cmdline: quiet splash cryptdevice=PARTUUID=f278d7fb-7688-48e7-97eb-6de149f36519:root cryptkey=UUID=5d5a6d31-93ca-4c9b-85d1-c7ae79127b1d:ext4:ssd512.key root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=/@/.snapshots/2/snapshot rw rootfstype=btrfs ``` Broken (current): ``` kernel_cmdline: quiet splash cryptdevice=PARTUUID=f278d7fb-7688-48e7-97eb-6de149f36519:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs ``` Missing parameter: `cryptkey=UUID=5d5a6d31-93ca-4c9b-85d1-c7ae79127b1d:ext4:ssd512.key` `/boot/limine.conf` modified at exactly update time: `Sep 27 14:23` Probably bootloader config generation should preserve custom `cryptkey` parameters during updates somehow...
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.