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.
Add Virtual Keyboard Support at Login Screen
Reported by ardfard · filed Oct 27, 2025Closed upstream on 2025-10-27 by dhh. 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
What do you need?
It would be helpful if Omarchy provided an on-screen (virtual) keyboard option at the login screen.
Right now, Bluetooth keyboards cannot be used before login since Bluetooth services are not available. A wired keyboard isn’t an option in my setup due to a faulty USB Type-C port, which makes it impossible to enter the password at login.
Having a virtual keyboard available at the login screen would solve this problem. It would also improve accessibility by offering a fallback input method for users who cannot use a physical keyboard.
Ideally, the virtual keyboard (for example, onboard or florence) could appear automatically when no keyboard input is detected, or be toggled manually if preferred.
View raw text
### What do you need? It would be helpful if Omarchy provided an on-screen (virtual) keyboard option at the login screen. Right now, Bluetooth keyboards cannot be used before login since Bluetooth services are not available. A wired keyboard isn’t an option in my setup due to a faulty USB Type-C port, which makes it impossible to enter the password at login. Having a virtual keyboard available at the login screen would solve this problem. It would also improve accessibility by offering a fallback input method for users who cannot use a physical keyboard. Ideally, the virtual keyboard (for example, onboard or florence) could appear automatically when no keyboard input is detected, or be toggled manually if preferred.
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.