Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-2310GitHub issuePublicReceived

Login decrypto screen USB device compatibility

Reported by danfascia · filed Jul 18, 2025Closed upstream on 2025-09-14 by ryanrhughes. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

Login decrypto screen USB device compatibilityrevision 1 · captured 2026-10-04 11:26 UTC via poll

The Omarchy ASCII login screen on system boot does not recognise common USB input devices that are expected to work for password input - 2.5G wireless keyboard adapters, USBC wired keyboard.

The same devices work fine for the BIOS boot (Beelink SER8) which proves that they are somehow being disabled for the password input screen.

Really strange bug but super frustrating resulting in system lockout

View raw text
The Omarchy ASCII login screen on system boot does not recognise common USB input devices that are expected to work for password input - 2.5G wireless keyboard adapters, USBC wired keyboard.

The same devices work fine for the BIOS boot (Beelink SER8) which proves that they are somehow being disabled for the password input screen.

Really strange bug but super frustrating resulting in system lockout

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.