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-1627GitHub issuePublicFixed

Display panel can't persistently turn off internal display — Omarchy watcher reverts it

Reported by EZHatETHZ · filed Aug 20, 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

Display panel can't persistently turn off internal display — Omarchy watcher reverts itrevision 1 · captured 2026-09-28 21:29 UTC via poll

System

  • Omarchy 4.0.0-1
  • Hyprland 0.56.2 (v0.56.2, commit efb5099)
  • ASUS ROG Zephyrus G14 GA403UI / AMD Ryzen 9 8945HS w/ Radeon 780M

What happened

In the Display panel (bar monitor icon → "DISPLAYS"), toggling off the internal laptop display works only momentarily; Omarchy's omarchy-hyprland-monitor-watch re-enables it within seconds whenever an external monitor is active.

Expected

Turning off the internal display from the panel should persist while docked, matching what omarchy hyprland monitor internal off does (and not fight the watcher).

Why it happens

Panel.qml:299-303, toggleDisplay() issues a raw

hyprctl keyword monitor <name>,disable

This doesn't create Omarchy's persistent disable flag at ~/.local/state/omarchy/toggles/hypr/internal-monitor-disable.lua. The watcher (omarchy-hyprland-monitor-clamshell → enable_internal) therefore re-enables it, since no manual-disable flag is present.

Suggested fix

In the Display panel, when toggling off an internal (eDP|LVDS|DSI-) monitor while an external is active, call omarchy-hyprland-monitor-internal off instead of the raw keyword (and mirror on/recover semantics), so it cooperates with the clamshell watcher.

Steps to reproduce

  1. Dock / connect an external monitor.
  2. Open Display panel → DISPLAYS → click your internal display row to disable it.
  3. Observe it re-enables within ~2s (watcher poll) while docked.
View raw text
## System
- Omarchy 4.0.0-1
- Hyprland 0.56.2 (v0.56.2, commit `efb5099`)
- ASUS ROG Zephyrus G14 GA403UI / AMD Ryzen 9 8945HS w/ Radeon 780M

## What happened
In the Display panel (bar monitor icon → "DISPLAYS"), toggling off the internal laptop display works only momentarily; Omarchy's `omarchy-hyprland-monitor-watch` re-enables it within seconds whenever an external monitor is active.

## Expected
Turning off the internal display from the panel should persist while docked, matching what `omarchy hyprland monitor internal off` does (and not fight the watcher).

## Why it happens
`Panel.qml:299-303`, `toggleDisplay()` issues a raw

```
hyprctl keyword monitor <name>,disable
```

This doesn't create Omarchy's persistent disable flag at `~/.local/state/omarchy/toggles/hypr/internal-monitor-disable.lua`. The watcher (`omarchy-hyprland-monitor-clamshell` → `enable_internal`) therefore re-enables it, since no manual-disable flag is present.

## Suggested fix
In the Display panel, when toggling off an internal (`eDP|LVDS|DSI-`) monitor while an external is active, call `omarchy-hyprland-monitor-internal off` instead of the raw keyword (and mirror `on`/recover semantics), so it cooperates with the clamshell watcher.

## Steps to reproduce
1. Dock / connect an external monitor.
2. Open Display panel → DISPLAYS → click your internal display row to disable it.
3. Observe it re-enables within ~2s (watcher poll) while docked.

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

  • Fixed bypr/7146· confirmed

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