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-596GitHub issuePublicDecided· Out of scope

SwitchToGreeter freezes the session: greeter relaunch targets the occupied VT (HELPER_TTY_ERROR)

Reported by MAXIDEA · filed Sep 13, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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

SwitchToGreeter freezes the session: greeter relaunch targets the occupied VT (HELPER_TTY_ERROR)revision 1 · captured 2026-09-28 21:23 UTC via poll

System details

AMD Ryzen 7 5700U (HP Laptop 17-cp0xxx), AMD Radeon Lucienne iGPU, Omarchy 4.0.3-1, kernel 7.2.3-arch1-3, Hyprland 0.56.2, SDDM 0.21.0-7 (Wayland greeter)

What's wrong?

Summary: calling SwitchToGreeter on the SDDM D-Bus seat freezes the whole display and requires a hard power-off. The seat advertises CanSwitch=true, so launchers and scripts reasonably offer fast user switching, but the relaunched greeter targets the already-occupied VT instead of a free one.

Steps to reproduce:

  1. Boot Omarchy 4.0.3 with the default SDDM setup (DisplayServer=wayland, greeter compositor start-hyprland, no autologin)
  2. Log into the Hyprland session as any user
  3. Run:
busctl --system call org.freedesktop.DisplayManager /org/freedesktop/DisplayManager/Seat0 \
  org.freedesktop.DisplayManager.Seat SwitchToGreeter

(the seat property CanSwitch is true, so this call looks legitimate)

  1. The screen freezes immediately; only a hard power-off recovers the machine

Journal excerpt (previous boot, sddm):

sddm-helper[83653]: Failed to take control of "/dev/tty1" ("max"): Operation not permitted
sddm[962]: Greeter stopped. SDDM::Auth::HELPER_TTY_ERROR
sddm[962]: Jumping to VT 1
sddm[962]: VT mode didn't need to be fixed
sddm[962]: Removing display SDDM::Display(0x7fbd2000d1f0) ...
sddm[962]: Jumping to VT 1

SDDM allocates VT 1 for the new greeter even though VT 1 is the active session's VT; the greeter helper then fails to take control of the tty (Operation not permitted), exits with HELPER_TTY_ERROR, and the compositor loses the display. No greeter ever appears on a second VT.

Expected: SwitchToGreeter starts the greeter on a free VT (fast user switching), or CanSwitch reports false so callers know switching is unsupported.

Workaround: don't call SwitchToGreeter; start the second user's session manually from a spare TTY (uwsm start), which works fine.

Full omarchy debug --no-sudo output available on request (754 lines) — happy to attach or upload to logs.omarchy.org.

View raw text
### System details

AMD Ryzen 7 5700U (HP Laptop 17-cp0xxx), AMD Radeon Lucienne iGPU, Omarchy 4.0.3-1, kernel 7.2.3-arch1-3, Hyprland 0.56.2, SDDM 0.21.0-7 (Wayland greeter)

### What's wrong?

**Summary:** calling `SwitchToGreeter` on the SDDM D-Bus seat freezes the whole display and requires a hard power-off. The seat advertises `CanSwitch=true`, so launchers and scripts reasonably offer fast user switching, but the relaunched greeter targets the already-occupied VT instead of a free one.

**Steps to reproduce:**

1. Boot Omarchy 4.0.3 with the default SDDM setup (`DisplayServer=wayland`, greeter compositor `start-hyprland`, no autologin)
2. Log into the Hyprland session as any user
3. Run:

```
busctl --system call org.freedesktop.DisplayManager /org/freedesktop/DisplayManager/Seat0 \
  org.freedesktop.DisplayManager.Seat SwitchToGreeter
```

(the seat property `CanSwitch` is `true`, so this call looks legitimate)

4. The screen freezes immediately; only a hard power-off recovers the machine

**Journal excerpt (previous boot, sddm):**

```
sddm-helper[83653]: Failed to take control of "/dev/tty1" ("max"): Operation not permitted
sddm[962]: Greeter stopped. SDDM::Auth::HELPER_TTY_ERROR
sddm[962]: Jumping to VT 1
sddm[962]: VT mode didn't need to be fixed
sddm[962]: Removing display SDDM::Display(0x7fbd2000d1f0) ...
sddm[962]: Jumping to VT 1
```

SDDM allocates VT 1 for the new greeter even though VT 1 is the active session's VT; the greeter helper then fails to take control of the tty (`Operation not permitted`), exits with `HELPER_TTY_ERROR`, and the compositor loses the display. No greeter ever appears on a second VT.

**Expected:** `SwitchToGreeter` starts the greeter on a free VT (fast user switching), or `CanSwitch` reports `false` so callers know switching is unsupported.

**Workaround:** don't call `SwitchToGreeter`; start the second user's session manually from a spare TTY (`uwsm start`), which works fine.

Full `omarchy debug --no-sudo` output available on request (754 lines) — happy to attach or upload to logs.omarchy.org.

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 12:52 UTC