Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1475GitHub issuePublicDecided· Out of scope

Logout from menu doesn't end session — SDDM uses non-uwsm session

Reported by nightdevil00 · filed Aug 25, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 5 days ago.

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

Logout from menu doesn't end session — SDDM uses non-uwsm sessionrevision 1 · captured 2026-09-28 21:24 UTC via poll

Description

The logout option from the Omarchy menu closes all windows but does not actually end the Wayland session. The user is left on an empty desktop.

Root Cause

SDDM's autologin config (/etc/sddm.conf.d/00-autologin.conf) sets Session=hyprland.desktop, which starts Hyprland directly via the start-hyprland watchdog — not through uwsm.

The logout script (omarchy-system-logout) runs uwsm stop to terminate the session, but since uwsm is not managing the session, it silently fails:

uwsm[24305]: Stopping compositor...
uwsm[24305]: Compositor is not running.

The window-close and OSD steps still execute, but the session never ends.

Steps to Reproduce

  1. Boot into Omarchy with SDDM autologin
  2. Open the Omarchy menu (Super+Escape)
  3. Navigate to System > Logout
  4. All windows close but the session remains active

Expected Behavior

The session should end and return to the SDDM greeter.

Fix

Change the session in /etc/sddm.conf.d/00-autologin.conf from:

Session=hyprland.desktop

to:

Session=hyprland-uwsm.desktop

The hyprland-uwsm.desktop file already exists in /usr/share/wayland-sessions/ and uses uwsm start -e -D Hyprland hyprland.desktop.

System Details

  • Omarchy: 4.0.1-1
  • uwsm: 0.26.7
  • Hyprland: 0.56.2
  • Distro: Omarchy on Arch Linux
  • Display Manager: SDDM
View raw text
## Description

The logout option from the Omarchy menu closes all windows but does not actually end the Wayland session. The user is left on an empty desktop.

## Root Cause

SDDM's autologin config (`/etc/sddm.conf.d/00-autologin.conf`) sets `Session=hyprland.desktop`, which starts Hyprland directly via the `start-hyprland` watchdog — **not** through uwsm.

The logout script (`omarchy-system-logout`) runs `uwsm stop` to terminate the session, but since uwsm is not managing the session, it silently fails:

```
uwsm[24305]: Stopping compositor...
uwsm[24305]: Compositor is not running.
```

The window-close and OSD steps still execute, but the session never ends.

## Steps to Reproduce

1. Boot into Omarchy with SDDM autologin
2. Open the Omarchy menu (Super+Escape)
3. Navigate to System > Logout
4. All windows close but the session remains active

## Expected Behavior

The session should end and return to the SDDM greeter.

## Fix

Change the session in `/etc/sddm.conf.d/00-autologin.conf` from:

```
Session=hyprland.desktop
```

to:

```
Session=hyprland-uwsm.desktop
```

The `hyprland-uwsm.desktop` file already exists in `/usr/share/wayland-sessions/` and uses `uwsm start -e -D Hyprland hyprland.desktop`.

## System Details

- Omarchy: 4.0.1-1
- uwsm: 0.26.7
- Hyprland: 0.56.2
- Distro: Omarchy on Arch Linux
- Display Manager: SDDM

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 08:45 UTC