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.
Password Desync Between sudo and Login Session
Reported by HanzGeeratz · filed Mar 17, 2026Closed upstream on 2026-03-18 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
Mac pro 6.1 - Latest Omarchy version
What's wrong?
There appears to be a disconnect between the local authentication used for elevated privileges (sudo) and the system's primary login credentials. When executing the passwd command, the password for sudo is updated successfully, but the change does not reflect on the login screen/Display Manager.
The system continues to require the old password for login while requiring the new password for terminal-based sudo actions.
Steps to Reproduce
Open a terminal session.
Run passwd and follow the prompts to update the user password.
Execute any command using sudo (e.g., sudo apt update or sudo systemctl status).
Result: The new password is required and accepted.
Lock the session or logout.
Attempt to log back in using the new password.
Result: Authentication fails.
Attempt to log in using the old password.
Result: Authentication succeeds.
Expected Behavior
The passwd command should update the authentication token globally for the user across both the Display Manager (Login) and the local shadow file/PAM modules used by sudo.
Actual Behavior
The authentication tokens have become decoupled. The system is essentially maintaining two separate password states for the same user.
View raw text
### System details Mac pro 6.1 - Latest Omarchy version ### What's wrong? There appears to be a disconnect between the local authentication used for elevated privileges (sudo) and the system's primary login credentials. When executing the passwd command, the password for sudo is updated successfully, but the change does not reflect on the login screen/Display Manager. The system continues to require the old password for login while requiring the new password for terminal-based sudo actions. **Steps to Reproduce** Open a terminal session. Run passwd and follow the prompts to update the user password. Execute any command using sudo (e.g., sudo apt update or sudo systemctl status). Result: The new password is required and accepted. Lock the session or logout. Attempt to log back in using the new password. Result: Authentication fails. Attempt to log in using the old password. Result: Authentication succeeds. **Expected Behavior** The passwd command should update the authentication token globally for the user across both the Display Manager (Login) and the local shadow file/PAM modules used by sudo. **Actual Behavior** The authentication tokens have become decoupled. The system is essentially maintaining two separate password states for the same user.
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.