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.
Feature Request: Support for Display Managers (e.g., SDDM)
Reported by goslynn · filed Aug 15, 2025Closed upstream on 2025-08-22 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
Feature Request: Support for Display Managers (e.g., SDDM)
Context
Currently, Omarchy relies on its own seamless-login systemd service to launch Hyprland directly on tty1. While this works, it bypasses standard Linux workflows where a Display Manager (DM) such as SDDM, GDM, LightDM is responsible for handling user sessions, authentication, and session startup.
On my system (Arch Linux with Omarchy), I wanted to use SDDM as the primary login manager instead of seamless-login. However, when disabling seamless-login, all Omarchy-provided binaries (omarchy-menu, omarchy-toggle-nightlight, omarchy-toggle-idle, omarchy-cmd-screenshot, etc.) stopped working properly after logging in via SDDM → Hyprland session.
Problems observed
1. Omarchy binaries are not automatically initialized when the session is started through SDDM.
2. Hyprland bindings that call omarchy-* commands no longer work unless I manually source or run the binaries.
3. The session feels incomplete compared to when it is started through seamless-login because the helpers (idle, nightlight, menus, themes) are not spawned automatically.
Why support Display Managers?
- Many users prefer to use SDDM/GDM/LightDM for consistent graphical login experience (multi-session support, remote logins, theming).
- seamless-login works, but it conflicts with standard Linux expectations (e.g., switching sessions, logging out back to DM).
- Using a DM also simplifies desktop switching (Xfce, GNOME, Hyprland, etc.) without needing to enable/disable seamless-login.
> Personal note: In my case, I specifically need to be able to switch to an X11 environment because at work I often use legacy software that does not run well (or at all) under Wayland — for example, iReport. Without DM support, switching between Hyprland (Wayland) and an X11 desktop is much harder.
Proposal
- Provide a systemd user service (e.g. omarchy-session.service) that runs automatically when the user logs into Hyprland via a DM.
- This service would initialize all Omarchy helpers (omarchy-toggle-idle, omarchy-menu, omarchy-theme-bg-next, etc.) so that bindings continue to work as expected.
- Optionally provide an environment setup script (similar to what seamless-login does internally) that can be sourced by ~/.xprofile, ~/.zprofile, or Hyprland’s exec-once entries.
Benefit
This would decouple Omarchy from a hard dependency on seamless-login and make it fully compatible with SDDM and other display managers, giving users the choice of login experience without losing Omarchy’s integrated tooling.
View raw text
### Feature Request: Support for Display Managers (e.g., SDDM) **Context** Currently, Omarchy relies on its own `seamless-login` systemd service to launch Hyprland directly on `tty1`. While this works, it bypasses standard Linux workflows where a **Display Manager** (DM) such as **SDDM, GDM, LightDM** is responsible for handling user sessions, authentication, and session startup. On my system (Arch Linux with Omarchy), I wanted to use **SDDM** as the primary login manager instead of `seamless-login`. However, when disabling `seamless-login`, all Omarchy-provided binaries (`omarchy-menu`, `omarchy-toggle-nightlight`, `omarchy-toggle-idle`, `omarchy-cmd-screenshot`, etc.) stopped working properly after logging in via SDDM → Hyprland session. --- **Problems observed** 1. Omarchy binaries are not automatically initialized when the session is started through SDDM. 2. Hyprland bindings that call `omarchy-*` commands no longer work unless I manually source or run the binaries. 3. The session feels incomplete compared to when it is started through `seamless-login` because the helpers (idle, nightlight, menus, themes) are not spawned automatically. --- **Why support Display Managers?** - Many users prefer to use **SDDM/GDM/LightDM** for consistent graphical login experience (multi-session support, remote logins, theming). - `seamless-login` works, but it conflicts with standard Linux expectations (e.g., switching sessions, logging out back to DM). - Using a DM also simplifies desktop switching (Xfce, GNOME, Hyprland, etc.) without needing to enable/disable `seamless-login`. > **Personal note**: In my case, I specifically need to be able to switch to an **X11 environment** because at work I often use legacy software that does not run well (or at all) under Wayland — for example, **iReport**. Without DM support, switching between Hyprland (Wayland) and an X11 desktop is much harder. --- **Proposal** - Provide a **systemd user service** (e.g. `omarchy-session.service`) that runs automatically when the user logs into Hyprland via a DM. - This service would initialize all Omarchy helpers (`omarchy-toggle-idle`, `omarchy-menu`, `omarchy-theme-bg-next`, etc.) so that bindings continue to work as expected. - Optionally provide an **environment setup script** (similar to what `seamless-login` does internally) that can be sourced by `~/.xprofile`, `~/.zprofile`, or Hyprland’s `exec-once` entries. --- **Benefit** This would decouple Omarchy from a hard dependency on `seamless-login` and make it fully compatible with **SDDM and other display managers**, giving users the choice of login experience without losing Omarchy’s integrated tooling.
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.