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.
Omarchy not booting after update to 3.1.0
Reported by TheYoxy · filed Oct 20, 2025Closed upstream on 2026-02-01 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
System details
Omarchy 3.1, Intel i9-10850K, NVIDIA RTX 3080
What's wrong?
After upgrading to 3.1, i have a weird issue where the system was hanging on boot.
It appears that plymouth-quit-wait service is hanging for something, but i couldn't find what.
When manually stopping it with systemctl stop plymouth-quit-wait, the boot process continues and i am able to reach hyprland.
I had a quick look to the log files, but I couldn't find anything relevant that could explain why the service was hanging.
As a quickfix, I've just disabled the service itself, waiting for more info before re-enabling it again
Also another point I've seen, maybe because I upgraded an existing arch installation to omarchy, if there is a sddm configuration file already existing in the sddm folder, specially named default.conf, it uses this old configuration file instead of the newly created autologin.conf
View raw text
### System details Omarchy 3.1, Intel i9-10850K, NVIDIA RTX 3080 ### What's wrong? After upgrading to 3.1, i have a weird issue where the system was hanging on boot. It appears that plymouth-quit-wait service is hanging for something, but i couldn't find what. When manually stopping it with `systemctl stop plymouth-quit-wait`, the boot process continues and i am able to reach hyprland. I had a quick look to the log files, but I couldn't find anything relevant that could explain why the service was hanging. > [!note] > As a quickfix, I've just disabled the service itself, waiting for more info before re-enabling it again Also another point I've seen, maybe because I upgraded an existing arch installation to omarchy, if there is a sddm configuration file already existing in the sddm folder, specially named `default.conf`, it uses this old configuration file instead of the newly created `autologin.conf`
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.