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

SDDM’s Hyprland compositor repeatedly crashes with SIGSEGV as the login greeter exits after successful authentication

Reported by rclinux · filed Sep 11, 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

SDDM’s Hyprland compositor repeatedly crashes with SIGSEGV as the login greeter exits after successful authenticationrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

AMD Ryzen 9 9950X3D, NVIDIA GeForce RTX 5080 (driver 610.57.04), Omarchy 4.0.3, kernel 7.2.3-arch1- 3, Hyprland 0.56.2-2, Aquamarine 0.15.0-2, SDDM 0.21.0-7, omarchy-settings 4.0.3-1.

What's wrong?

SDDM’s Hyprland compositor repeatedly crashes with SIGSEGV when the login greeter exits after
successful authentication. The Omarchy desktop session starts successfully afterward, so this is
currently non-blocking.

### Steps to reproduce

  1. Boot to the SDDM login screen.
  2. Log in to the Omarchy session.
  3. Check coredumpctl list and journalctl -b -u sddm.

Expected: the greeter compositor exits cleanly.
Actual: a Hyprland core dump is recorded during the transition to the desktop.

Eight Hyprland crashes belonging to the sddm user were recorded on September 11, 2026. The latest
crash was inspected and confirmed to occur during greeter shutdown.

### Crash evidence

  User: sddm
  Signal: SIGSEGV
  Command: Hyprland --watchdog-fd 4 --config /usr/share/sddm/hyprland.lua

Relevant stack frames, with C++ names demangled for readability:

  Aquamarine::CDRMBackend::flushAsyncCommitEvents()
  Aquamarine::CDRMBackend::cancelAsyncOutput(...)
  Aquamarine::SDRMConnector::disconnect()
  Aquamarine::CDRMBackend::~CDRMBackend()
  Aquamarine::CBackend::~CBackend()
  ...
  __cxa_finalize
  exit

At the same timestamp, SDDM logs successful authentication, the greeter stopping, and the user
session starting successfully.

### Greeter configuration

  [General]
  DisplayServer=wayland

  [Wayland]
  CompositorCommand=start-hyprland -- --config /usr/share/sddm/hyprland.lua

Both /etc/sddm.conf.d/10-wayland.conf and /usr/share/sddm/hyprland.lua are owned by `omarchy-
settings`.

The stack suggests a crash during Aquamarine graphics-backend cleanup. The underlying cause has not
been established; it may belong upstream in Hyprland/Aquamarine. Reporting here because it affects
Omarchy’s packaged login-screen setup.

No raw core dump is attached.

View raw text
### System details

AMD Ryzen 9 9950X3D, NVIDIA GeForce RTX 5080 (driver 610.57.04), Omarchy 4.0.3, kernel 7.2.3-arch1-   3, Hyprland 0.56.2-2, Aquamarine 0.15.0-2, SDDM 0.21.0-7, omarchy-settings 4.0.3-1.

### What's wrong?

 SDDM’s Hyprland compositor repeatedly crashes with SIGSEGV when the login greeter exits after
  successful authentication. The Omarchy desktop session starts successfully afterward, so this is
  currently non-blocking.

  ### Steps to reproduce

  1. Boot to the SDDM login screen.
  2. Log in to the Omarchy session.
  3. Check `coredumpctl list` and `journalctl -b -u sddm`.

  Expected: the greeter compositor exits cleanly.
  Actual: a Hyprland core dump is recorded during the transition to the desktop.

  Eight Hyprland crashes belonging to the `sddm` user were recorded on September 11, 2026. The latest
  crash was inspected and confirmed to occur during greeter shutdown.

  ### Crash evidence

  ```text
  User: sddm
  Signal: SIGSEGV
  Command: Hyprland --watchdog-fd 4 --config /usr/share/sddm/hyprland.lua
  ```

  Relevant stack frames, with C++ names demangled for readability:

  ```text
  Aquamarine::CDRMBackend::flushAsyncCommitEvents()
  Aquamarine::CDRMBackend::cancelAsyncOutput(...)
  Aquamarine::SDRMConnector::disconnect()
  Aquamarine::CDRMBackend::~CDRMBackend()
  Aquamarine::CBackend::~CBackend()
  ...
  __cxa_finalize
  exit
  ```

  At the same timestamp, SDDM logs successful authentication, the greeter stopping, and the user
  session starting successfully.

  ### Greeter configuration

  ```ini
  [General]
  DisplayServer=wayland

  [Wayland]
  CompositorCommand=start-hyprland -- --config /usr/share/sddm/hyprland.lua
  ```

  Both `/etc/sddm.conf.d/10-wayland.conf` and `/usr/share/sddm/hyprland.lua` are owned by `omarchy-
  settings`.

  The stack suggests a crash during Aquamarine graphics-backend cleanup. The underlying cause has not
  been established; it may belong upstream in Hyprland/Aquamarine. Reporting here because it affects
  Omarchy’s packaged login-screen setup.

  No raw core dump is attached.

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:01 UTC