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

Display plugin unable to change brightness for mirrored display monitors

Reported by knappkevin · filed Sep 10, 2026 · 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 plugin unable to change brightness for mirrored display monitorsrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Tested with a ASUS and Samsung monitor over HDMI, Omarchy 4.0.3-1, Linux 7.2.3, ddcutil installed

What's wrong?

Problem

My laptop screen is mirrored to an external monitor (over HDMI but doubt its relevant). The default display plugin only shows and can only show the the brightness slider for the laptop but never the mirrored external monitor. It is not possible to change focus from the laptop to the monitor to make it behave as expected.

Why, as I understand it

The plugin queries omarchy-monitor-state, which queries brightness from the focused monitor. When screens are mirrored, Hyprland keeps only the internal display focused, the laptop acting as the source, but never the external mirrored monitor as it is just a mirror. The DDC/CI path in omarchy-brightness-display is never reached from the UI.

Suggested solution

Any UI solution that allows for mirrored monitors to get their brightness changed too. I know there are a lot of great display plugins in the marketplace too but I made a clone of the default that is focused purely on bug fixes below. I'd love to open an appropriate PR for it if it gets your blessing.

https://github.com/knappkevin/mirror-display-brightness
It does also fix another display plugin bug that couldn't toggle the enable/disable of monitors, which seemed to be an intended part of the code. But I don't care about that personally.

View raw text
### System details

Tested with a ASUS and Samsung monitor over HDMI, Omarchy 4.0.3-1, Linux 7.2.3, ddcutil installed

### What's wrong?

## Problem

My laptop screen is mirrored to an external monitor (over HDMI but doubt its relevant). The default display plugin only shows and can only show the the brightness slider for the laptop but never the mirrored external monitor. It is not possible to change focus from the laptop to the monitor to make it behave as expected.

## Why, as I understand it

The plugin queries omarchy-monitor-state, which queries brightness from the focused monitor. When screens are mirrored, Hyprland keeps only the internal display focused, the laptop acting as the source, but never the external mirrored monitor as it is just a mirror. The DDC/CI path in omarchy-brightness-display is never reached from the UI.

## Suggested solution

 Any UI solution that allows for mirrored monitors to get their brightness changed too. I know there are a lot of great display plugins in the marketplace too but I made a [clone of the default that is focused purely on bug fixes](https://github.com/knappkevin/mirror-display-brightness) below. I'd love to open an appropriate PR for it if it gets your blessing.

https://github.com/knappkevin/mirror-display-brightness
It does also fix another display plugin bug that couldn't toggle the enable/disable of monitors, which seemed to be an intended part of the code. But I don't care about that personally.

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 11:43 UTC