Proof Portal

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-4459GitHub issuePublicReceived

Omarchy toggle load order makes user looknfeel.conf unable to override toggle settings.

Reported by xicubed · filed Jun 10, 2026Closed upstream on 2026-08-15 by its own reporter xicubed. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

Omarchy toggle load order makes user looknfeel.conf unable to override toggle settings.revision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Omarchy 3.8.2. Hyprland 0.55.2 (Wayland). ghostty 1.3.1-arch2

What's wrong?

I went to open a single window on my desktop and its shunk now because I have a wide monitor. Not a bad design decision, just not for me so I went to over-ride it in ~/.conf/hypr/looknfeel.conf (by adding single_window_aspect_ratio = 0 0 to the layout section) but it gets overridden by ~/.local/state/omarchy/toggles/hypr/*.conf based on the load order in ~/.config/hypr/hyprland.conf

Once I put my looknfeel.conf again at the bottom of the hyprland.conf it worked as expected with a new window filling the screen. Maybe the toggles should be after the defaults but before the customs?

# Learn how to configure Hyprland: https://wiki.hyprland.org/Configuring/

# Use defaults Omarchy defaults (but don't edit these directly!)
source = ~/.local/share/omarchy/default/hypr/autostart.conf
source = ~/.local/share/omarchy/default/hypr/bindings/media.conf
source = ~/.local/share/omarchy/default/hypr/bindings/clipboard.conf
source = ~/.local/share/omarchy/default/hypr/bindings/tiling-v2.conf
source = ~/.local/share/omarchy/default/hypr/bindings/utilities.conf
source = ~/.local/share/omarchy/default/hypr/envs.conf
source = ~/.local/share/omarchy/default/hypr/looknfeel.conf
source = ~/.local/share/omarchy/default/hypr/input.conf
source = ~/.local/share/omarchy/default/hypr/windows.conf
source = ~/.config/omarchy/current/theme/hyprland.conf

# Change your own setup in these files (and overwrite any settings from defaults!)
source = ~/.config/hypr/monitors.conf
source = ~/.config/hypr/input.conf
source = ~/.config/hypr/bindings.conf
source = ~/.config/hypr/envs.conf
source = ~/.config/hypr/looknfeel.conf
source = ~/.config/hypr/autostart.conf

# NVIDIA environment variables
env = NVD_BACKEND,direct
env = LIBVA_DRIVER_NAME,nvidia
env = __GLX_VENDOR_LIBRARY_NAME,nvidia```

# Toggle config flags dynamically
source = ~/.local/state/omarchy/toggles/hypr/*.conf

# 2026-06-10 mal toggles overwriting my looknfeel; reloading
source = ~/.config/hypr/looknfeel.conf
View raw text
### System details

Omarchy 3.8.2. Hyprland 0.55.2 (Wayland). ghostty 1.3.1-arch2

### What's wrong?

I went to open a single window on my desktop and its shunk now because I have a wide monitor. Not a bad design decision, just not for me so I went to over-ride it in `~/.conf/hypr/looknfeel.conf` (by adding `single_window_aspect_ratio = 0 0` to the layout section) but it gets overridden by `~/.local/state/omarchy/toggles/hypr/*.conf` based on the load order in `~/.config/hypr/hyprland.conf`

Once I put my looknfeel.conf again at the bottom of the hyprland.conf it worked as expected with a new window filling the screen. Maybe the toggles should be after the defaults but before the customs?

```~ ❯ cat ~/.config/hypr/hyprland.conf
# Learn how to configure Hyprland: https://wiki.hyprland.org/Configuring/

# Use defaults Omarchy defaults (but don't edit these directly!)
source = ~/.local/share/omarchy/default/hypr/autostart.conf
source = ~/.local/share/omarchy/default/hypr/bindings/media.conf
source = ~/.local/share/omarchy/default/hypr/bindings/clipboard.conf
source = ~/.local/share/omarchy/default/hypr/bindings/tiling-v2.conf
source = ~/.local/share/omarchy/default/hypr/bindings/utilities.conf
source = ~/.local/share/omarchy/default/hypr/envs.conf
source = ~/.local/share/omarchy/default/hypr/looknfeel.conf
source = ~/.local/share/omarchy/default/hypr/input.conf
source = ~/.local/share/omarchy/default/hypr/windows.conf
source = ~/.config/omarchy/current/theme/hyprland.conf

# Change your own setup in these files (and overwrite any settings from defaults!)
source = ~/.config/hypr/monitors.conf
source = ~/.config/hypr/input.conf
source = ~/.config/hypr/bindings.conf
source = ~/.config/hypr/envs.conf
source = ~/.config/hypr/looknfeel.conf
source = ~/.config/hypr/autostart.conf

# NVIDIA environment variables
env = NVD_BACKEND,direct
env = LIBVA_DRIVER_NAME,nvidia
env = __GLX_VENDOR_LIBRARY_NAME,nvidia```

# Toggle config flags dynamically
source = ~/.local/state/omarchy/toggles/hypr/*.conf

# 2026-06-10 mal toggles overwriting my looknfeel; reloading
source = ~/.config/hypr/looknfeel.conf

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.