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 autologin + uwsm: session dies immediately (blank screen); uwsm reports graphical-session already active
Reported by pib-nbsmedia · filed Sep 1, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
- Hardware: Apple Mac mini (Macmini7,1)
- CPU: Intel Core i7-4578U
- GPU: Intel HD Graphics 5100 / Iris 5100 (Haswell-ULT, i915, PCI 8086:0a2e)
- Omarchy 4.0.2, Hyprland 0.56.2, SDDM 0.21.0, uwsm 0.26.7
- LUKS + btrfs, Limine UKI, SDDM autologin to the packaged Omarchy session
This may be easier to hit on slower Intel Apple hardware (Haswell iGPU) than on current AMD/NVIDIA boxes. Same packaged session files; the failure is a race between the SDDM Wayland greeter compositor and uwsm start.
What's wrong?
After a normal boot (disk unlock), SDDM autologin starts the Omarchy session and the screen goes blank. No Hyprland. Recurs after every omarchy-settings / Omarchy update because the packaged session file is restored.
Journal (sanitized):
sddm: Session omarchy.desktop selected, command: "uwsm start -g -1 -e -D Hyprland hyprland.desktop"
sddm-helper: Starting Wayland user session: wayland-session "uwsm start -g -1 -e -D Hyprland hyprland.desktop"
uwsm: Selected compositor ID: hyprland.desktop
Command Line: /usr/bin/start-hyprland
uwsm: Matched 2 units, 1 active:
uwsm: graphical-session.target (Current graphical user session)
uwsm: A compositor or graphical-session* target is already active!
sddm: Auth: sddm-helper exited with 1Packaged combo:
/etc/sddm.conf.d/10-wayland.conf— greeterCompositorCommand=start-hyprland -- --config /usr/share/sddm/hyprland.luadefault/wayland-sessions/omarchy.desktop—Exec=uwsm start -g -1 -e -D Hyprland hyprland.desktop
SDDM starts a Hyprland greeter compositor, then autologin starts uwsm. uwsm sees graphical-session.target already active (no compositor for the user yet) and refuses to start. SDDM helper exits 1 → blank.
Workaround that restores a desktop: point the session Exec at /usr/bin/start-hyprland (no uwsm). That is overwritten on the next omarchy-settings upgrade.
This is not #8200 (logout with a non-uwsm session). Opposite failure: uwsm never gets to own the session. #8152 is a different install/PAM crash loop.
Expected: autologin should start Hyprland via uwsm even if a greeter compositor briefly activated graphical-session.target. Updates should not re-break a working session.
Not a support request — logs + a local workaround that is clobbered by the packaged desktop file.
View raw text
### System details
- Hardware: Apple Mac mini (Macmini7,1)
- CPU: Intel Core i7-4578U
- GPU: Intel HD Graphics 5100 / Iris 5100 (Haswell-ULT, i915, PCI 8086:0a2e)
- Omarchy 4.0.2, Hyprland 0.56.2, SDDM 0.21.0, uwsm 0.26.7
- LUKS + btrfs, Limine UKI, SDDM autologin to the packaged Omarchy session
This may be easier to hit on slower Intel Apple hardware (Haswell iGPU) than on current AMD/NVIDIA boxes. Same packaged session files; the failure is a race between the SDDM Wayland greeter compositor and `uwsm start`.
### What's wrong?
After a normal boot (disk unlock), SDDM autologin starts the Omarchy session and the screen goes **blank**. No Hyprland. Recurs after every `omarchy-settings` / Omarchy update because the packaged session file is restored.
Journal (sanitized):
```
sddm: Session omarchy.desktop selected, command: "uwsm start -g -1 -e -D Hyprland hyprland.desktop"
sddm-helper: Starting Wayland user session: wayland-session "uwsm start -g -1 -e -D Hyprland hyprland.desktop"
uwsm: Selected compositor ID: hyprland.desktop
Command Line: /usr/bin/start-hyprland
uwsm: Matched 2 units, 1 active:
uwsm: graphical-session.target (Current graphical user session)
uwsm: A compositor or graphical-session* target is already active!
sddm: Auth: sddm-helper exited with 1
```
Packaged combo:
- `/etc/sddm.conf.d/10-wayland.conf` — greeter `CompositorCommand=start-hyprland -- --config /usr/share/sddm/hyprland.lua`
- `default/wayland-sessions/omarchy.desktop` — `Exec=uwsm start -g -1 -e -D Hyprland hyprland.desktop`
SDDM starts a Hyprland greeter compositor, then autologin starts uwsm. uwsm sees `graphical-session.target` already active (no compositor for the user yet) and **refuses to start**. SDDM helper exits 1 → blank.
Workaround that restores a desktop: point the session `Exec` at `/usr/bin/start-hyprland` (no uwsm). That is overwritten on the next `omarchy-settings` upgrade.
This is **not** #8200 (logout with a non-uwsm session). Opposite failure: uwsm never gets to own the session. #8152 is a different install/PAM crash loop.
Expected: autologin should start Hyprland via uwsm even if a greeter compositor briefly activated `graphical-session.target`. Updates should not re-break a working session.
Not a support request — logs + a local workaround that is clobbered by the packaged desktop file.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.
- Out of scopeDecided by agents · verified · 2026-10-09 10:26 UTC