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.
Hyprland not allowing login
Reported by kridaydave · filed Aug 25, 2026Closed upstream on 2026-09-05 by its own reporter kridaydave. GitHub close reason: completed. Closed by its own reporter — not by itself 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
Lenovo IdeaPad 3, Omarchy-4
What's wrong?
Running the installation scripts manually via CLI (omarchy-apply-system --install-user <username> --first-install) provisions a user without setting an initial password hash or proper locker PAM entries. After setting a password via chroot, authentication succeeds, but the desktop session crashes instantly on start, respawning the login screen and falsely reporting authentication failure.
Steps to Reproduce:
Install Omarchy Quattro 4.0 using manual/backend script invocation (omarchy-apply-system).
Boot into the installed system.
Set user credentials via live environment chroot after discovering the uninitialized password.
Enter the correct password at the boot screen.
Observe the loading progress bar fill completely.
Observed Behavior:
Password Provisioning: Manual/scripted install bypasses GUI password creation, leaving the user with a locked/empty hash in /etc/shadow.
Lockout Cascade: Repeated login attempts trigger pam_faillock.so via /etc/pam.d/omarchy-lock-password, locking the user out entirely until manually cleared.
Session Crash Loop: Once a valid password is set, the loading bar fills completely. The screen cuts to black to launch Hyprland/Wayland, crashes immediately, and bounces back to the lock screen with a red lock icon(auth failed).
Trapped Recovery: Wayland intercepts VT-switching (Ctrl+Alt+F2..F6), and the Limine UKI configuration ignores standard rescue flags like init=/bin/bash, requiring a live USB for troubleshooting by pressing Ctrl+c during auto login as root since it doesn't allow for gracefully dropping before installation error caused by the recently merged synaptic issue.
Expected Behavior:
User creation scripts should require an initial password or explicitly warn if omitted.
Default PAM configs should prevent instant account lockouts on new installations.
Compositor failures should fall back gracefully to a display manager error log or drop to a functional TTY rather than infinitely looping at the lock screen.
Environment:
OS / Distribution: Omarchy Quattro 4.0
Compositor / Display Manager: Hyprland / SDDM / Hyprlock
GPU / Graphics: Intel Graphics (Mesa / Vulkan)
Bootloader & Storage: Limine UKI on LUKS-encrypted Btrfs (subvolume @)
View raw text
### System details Lenovo IdeaPad 3, Omarchy-4 ### What's wrong? Running the installation scripts manually via CLI (omarchy-apply-system --install-user <username> --first-install) provisions a user without setting an initial password hash or proper locker PAM entries. After setting a password via chroot, authentication succeeds, but the desktop session crashes instantly on start, respawning the login screen and falsely reporting authentication failure. **Steps to Reproduce:** Install Omarchy Quattro 4.0 using manual/backend script invocation (omarchy-apply-system). Boot into the installed system. Set user credentials via live environment chroot after discovering the uninitialized password. Enter the correct password at the boot screen. Observe the loading progress bar fill completely. **Observed Behavior:** Password Provisioning: Manual/scripted install bypasses GUI password creation, leaving the user with a locked/empty hash in /etc/shadow. Lockout Cascade: Repeated login attempts trigger pam_faillock.so via /etc/pam.d/omarchy-lock-password, locking the user out entirely until manually cleared. Session Crash Loop: Once a valid password is set, the loading bar fills completely. The screen cuts to black to launch Hyprland/Wayland, crashes immediately, and bounces back to the lock screen with a red lock icon(auth failed). Trapped Recovery: Wayland intercepts VT-switching (Ctrl+Alt+F2..F6), and the Limine UKI configuration ignores standard rescue flags like init=/bin/bash, requiring a live USB for troubleshooting by pressing Ctrl+c during auto login as root since it doesn't allow for gracefully dropping before installation error caused by the recently merged synaptic issue. **Expected Behavior:** User creation scripts should require an initial password or explicitly warn if omitted. Default PAM configs should prevent instant account lockouts on new installations. Compositor failures should fall back gracefully to a display manager error log or drop to a functional TTY rather than infinitely looping at the lock screen. **Environment:** OS / Distribution: Omarchy Quattro 4.0 Compositor / Display Manager: Hyprland / SDDM / Hyprlock GPU / Graphics: Intel Graphics (Mesa / Vulkan) Bootloader & Storage: Limine UKI on LUKS-encrypted Btrfs (subvolume @)
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.