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.
Installation fail when username is "root"
Reported by Sittlon · filed Oct 20, 2025Closed upstream on 2025-10-20 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?
The user has the opportunity to choose the username "root" in the installation. This results in an installation failure, which makes sense. But the output is a traceback of some python code. Only one line above the python traceback says: failed to adduser, root already exist.
Maybe an enhancement that the user cant even choose root in the first place?
View raw text
### What do you need? The user has the opportunity to choose the username "root" in the installation. This results in an installation failure, which makes sense. But the output is a traceback of some python code. Only one line above the python traceback says: failed to adduser, root already exist. Maybe an enhancement that the user cant even choose root in the first place?
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.