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.
SDDM authenticates empty username ("") after interrupted/resumed install — "User not known to the underlying authentication module"
Reported by gtech-pedrol · filed Aug 23, 2026Closed upstream on 2026-10-03 by the bot omarchybot, as not planned.
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
- Laptop: Lenovo Ideapad 330-15IKB (81FE) - CPU: Intel Core i7-8550U - GPU: NVIDIA GeForce MX150 - Omarchy version: 4.0 (Quattro) - Install method: Official ISO, full disk + LUKS - Note: Installation was interrupted multiple times during hardware phase and resumed via arch-chroot + omarchy-apply-system
What's wrong?
After completing a resumed installation (due to earlier failures in hardware scripts), the system boots correctly and unlocks the LUKS disk with the correct password.
However, the graphical SDDM login screen always fails with:
pam_unix(sddm:auth): check pass; user unknown
Authentication error: SDDM::Auth::ERROR_AUTHENTICATION "User not known to the underlying authentication module"
Authentication for user "" failedKey points:
- The user account myusername exists and works perfectly on TTY (Ctrl+Alt+F2).
- Password is correct (confirmed via passwd and TTY login).
- SDDM is trying to authenticate an empty username ("") instead of myusername.
- Adding DefaultUser=myusername in /etc/sddm.conf.d/ did not help.
- The Omarchy theme is active (Current=omarchy).
Workaround that worked:
Enabled autologin temporarily:
[Autologin]
User=myusername
Session=hyprlandExpected behavior:
SDDM should correctly detect and use the existing user myusername (especially on a single-user install), even after a resumed/interrupted installation.
View raw text
### System details - Laptop: Lenovo Ideapad 330-15IKB (81FE) - CPU: Intel Core i7-8550U - GPU: NVIDIA GeForce MX150 - Omarchy version: 4.0 (Quattro) - Install method: Official ISO, full disk + LUKS - Note: Installation was interrupted multiple times during hardware phase and resumed via arch-chroot + omarchy-apply-system ### What's wrong? After completing a resumed installation (due to earlier failures in hardware scripts), the system boots correctly and unlocks the LUKS disk with the correct password. However, the graphical SDDM login screen always fails with: ``` pam_unix(sddm:auth): check pass; user unknown Authentication error: SDDM::Auth::ERROR_AUTHENTICATION "User not known to the underlying authentication module" Authentication for user "" failed ``` Key points: - The user account `myusername` exists and works perfectly on TTY (Ctrl+Alt+F2). - Password is correct (confirmed via `passwd` and TTY login). - SDDM is trying to authenticate an **empty username** (`""`) instead of `myusername`. - Adding `DefaultUser=myusername` in `/etc/sddm.conf.d/` did not help. - The Omarchy theme is active (`Current=omarchy`). **Workaround that worked:** Enabled autologin temporarily: ```ini [Autologin] User=myusername Session=hyprland ``` **Expected behavior:** SDDM should correctly detect and use the existing user `myusername` (especially on a single-user install), even after a resumed/interrupted installation.
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.