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

Display panel brightness slider does not work with LG UltraGear evo 27GM950B-B

Reported by Murderlon · filed Aug 29, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 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 brightness slider does not work with LG UltraGear evo 27GM950B-Brevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

AMD Ryzen 7 8845HS with Radeon 780M Graphics (amdgpu), LG UltraGear evo 27GM950B-B connected via DisplayPort (DP-1), Omarchy 4.0.1-1, Hyprland 0.56.2, Linux 7.1.9-arch1-2, ddcutil 2.2.7.

Diagnostic log: https://logs.omarchy.org/6F0h7h

What's wrong?

The Display panel detects the external monitor and shows a brightness slider, but dragging the slider does not change the monitor's brightness. The panel also reports success because the underlying helper exits successfully, although the monitor's VCP brightness value remains unchanged.

This is reproducible with the packaged DDC helper:

$ ddcutil --bus 9 getvcp 10 --brief
VCP 10 C 100 100

$ omarchy-brightness-display --no-osd --monitor DP-1 70%
$ echo $?
0

$ ddcutil --bus 9 getvcp 10 --brief
VCP 10 C 100 100

The same monitor responds correctly when the DDC checks are not skipped:

$ ddcutil --bus 9 setvcp 10 70
$ ddcutil --bus 9 getvcp 10 --brief
VCP 10 C 70 100

The fast path used by Omarchy reproduces the failure:

$ ddcutil --bus 9 --skip-ddc-checks --noverify setvcp 10 70
$ ddcutil --bus 9 getvcp 10 --brief
VCP 10 C 100 100

The packaged helper /usr/share/omarchy/bin/omarchy-brightness-display-ddc currently invokes:

ddcutil --bus "$bus" --skip-ddc-checks --noverify setvcp 10 "$raw_target"

It appears that this monitor accepts the command without an error but ignores the write when --skip-ddc-checks is used. The normal ddcutil path successfully changes VCP 0x10. A possible fix would be to retry without --skip-ddc-checks when the requested value is not applied, or otherwise allow a per-monitor fallback.

The monitor is identified by ddcutil as LG ULTRAGEAR+, product code 23800, serial 605NTUWKV886, on I2C bus 9; VCP 0x10 is reported as writable with a range of 0–100.

Expected: dragging the Display panel brightness slider changes the physical monitor brightness.

Actual: the slider moves in the UI, but the physical brightness remains unchanged.

View raw text
## System details

AMD Ryzen 7 8845HS with Radeon 780M Graphics (amdgpu), LG UltraGear evo 27GM950B-B connected via DisplayPort (DP-1), Omarchy 4.0.1-1, Hyprland 0.56.2, Linux 7.1.9-arch1-2, ddcutil 2.2.7.

Diagnostic log: https://logs.omarchy.org/6F0h7h

## What's wrong?

The Display panel detects the external monitor and shows a brightness slider, but dragging the slider does not change the monitor's brightness. The panel also reports success because the underlying helper exits successfully, although the monitor's VCP brightness value remains unchanged.

This is reproducible with the packaged DDC helper:

```text
$ ddcutil --bus 9 getvcp 10 --brief
VCP 10 C 100 100

$ omarchy-brightness-display --no-osd --monitor DP-1 70%
$ echo $?
0

$ ddcutil --bus 9 getvcp 10 --brief
VCP 10 C 100 100
```

The same monitor responds correctly when the DDC checks are not skipped:

```text
$ ddcutil --bus 9 setvcp 10 70
$ ddcutil --bus 9 getvcp 10 --brief
VCP 10 C 70 100
```

The fast path used by Omarchy reproduces the failure:

```text
$ ddcutil --bus 9 --skip-ddc-checks --noverify setvcp 10 70
$ ddcutil --bus 9 getvcp 10 --brief
VCP 10 C 100 100
```

The packaged helper `/usr/share/omarchy/bin/omarchy-brightness-display-ddc` currently invokes:

```bash
ddcutil --bus "$bus" --skip-ddc-checks --noverify setvcp 10 "$raw_target"
```

It appears that this monitor accepts the command without an error but ignores the write when `--skip-ddc-checks` is used. The normal `ddcutil` path successfully changes VCP 0x10. A possible fix would be to retry without `--skip-ddc-checks` when the requested value is not applied, or otherwise allow a per-monitor fallback.

The monitor is identified by `ddcutil` as LG ULTRAGEAR+, product code 23800, serial 605NTUWKV886, on I2C bus 9; VCP 0x10 is reported as writable with a range of 0–100.

Expected: dragging the Display panel brightness slider changes the physical monitor brightness.

Actual: the slider moves in the UI, but the physical brightness remains unchanged.

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 09:55 UTC