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.
Brightness OSD shows but no change
Reported by tonyjr9 · filed Dec 29, 2025Closed upstream on 2026-01-14 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
System details
ASUS G513R laptop Radeon 680M + RTX 3060, acpi_video0 dummy
What's wrong?
Brightness control worked perfectly in Omarchy yesterday (Fn keys + OSD widget changed actual screen brightness). Today after reboot (no manual updates or config changes), keys trigger OSD but screen brightness stays fixed—no dimming/brightening occurs.
brightnessctl -d acpi_video0 set 10% changes the value (OSD updates), but screen brightness does not change at all. Gamma tools (wlsunset, gammastep) fail: "gamma control of output Unknown-1 failed" or "no outputs support gamma adjustment".
This is a regression: worked before, broken after reboot. Hardware confirmed stable (no artifacts/flicker).
Hardware:
- Laptop: ASUS ROG Strix G513R
- GPUs: NVIDIA RTX 3060 Mobile + AMD Radeon 680M iGPU (hybrid)
lspci -nn | grep -E 'VGA|Display'
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1)
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev c8)Current state:
uname -r
6.12.61-1-lts
ls /sys/class/backlight/
lrwxrwxrwx acpi_video0 -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.0/backlight/acpi_video0
brightnessctl --list
[full output as pasted; acpi_video0 shows but ineffective]
cat /proc/cmdline
quiet splash amdgpu.backlight=0 amdgpu.dcdebugmask=0x40000 acpi_backlight=video cryptdevice=PARTUUID=d83bfe1e-b07a-4e15-b271-1ea807036ec0:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfsTried fixes (no change):
- Kernel params: amdgpu.backlight=0, amdgpu.dcdebugmask=0x40000, acpi_backlight=video/native/none
- Switched to linux-lts (6.12.61-1-lts)
- Manual writes to /sys/class/backlight/acpi_video0/brightness
- brightnessctl binds in Hyprland config targeting acpi_video0
- wlsunset/gammastep (gamma unsupported on Unknown-1 output)
- asusctl install
Expected: Fn keys + OSD change actual screen brightness like yesterday.
Repro: Boot Omarchy → press Fn brightness keys → OSD moves, screen unchanged.
Happy to test patches/kernels/BIOS settings. Thanks![3][4][5]
View raw text
### System details ASUS G513R laptop Radeon 680M + RTX 3060, acpi_video0 dummy ### What's wrong? Brightness control worked perfectly in Omarchy yesterday (Fn keys + OSD widget changed actual screen brightness). Today after reboot (no manual updates or config changes), keys trigger OSD but screen brightness stays fixed—no dimming/brightening occurs. `brightnessctl -d acpi_video0 set 10%` changes the value (OSD updates), but screen brightness does not change at all. Gamma tools (wlsunset, gammastep) fail: "gamma control of output Unknown-1 failed" or "no outputs support gamma adjustment". This is a regression: worked before, broken after reboot. Hardware confirmed stable (no artifacts/flicker). **Hardware:** - Laptop: ASUS ROG Strix G513R - GPUs: NVIDIA RTX 3060 Mobile + AMD Radeon 680M iGPU (hybrid) ``` lspci -nn | grep -E 'VGA|Display' 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev c8) ``` **Current state:** ``` uname -r 6.12.61-1-lts ls /sys/class/backlight/ lrwxrwxrwx acpi_video0 -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.0/backlight/acpi_video0 brightnessctl --list [full output as pasted; acpi_video0 shows but ineffective] cat /proc/cmdline quiet splash amdgpu.backlight=0 amdgpu.dcdebugmask=0x40000 acpi_backlight=video cryptdevice=PARTUUID=d83bfe1e-b07a-4e15-b271-1ea807036ec0:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs ``` **Tried fixes (no change):** - Kernel params: `amdgpu.backlight=0`, `amdgpu.dcdebugmask=0x40000`, `acpi_backlight=video/native/none` - Switched to linux-lts (6.12.61-1-lts) - Manual writes to `/sys/class/backlight/acpi_video0/brightness` - brightnessctl binds in Hyprland config targeting acpi_video0 - wlsunset/gammastep (gamma unsupported on Unknown-1 output) - asusctl install **Expected:** Fn keys + OSD change actual screen brightness like yesterday. **Repro:** Boot Omarchy → press Fn brightness keys → OSD moves, screen unchanged. Happy to test patches/kernels/BIOS settings. Thanks![3][4][5] [1](https://github.com/basecamp/omarchy/discussions/3700) [2](https://github.com/basecamp/omarchy/discussions/3438) [3](https://forum.manjaro.org/t/unable-to-adjust-brightness-on-amd-cpu-with-integrated-gpu/41480) [4](https://wiki.archlinux.org/title/Backlight) [5](https://forum.manjaro.org/t/cannot-change-screen-brightness-nvidia-gpu/101817) [6](https://ppl-ai-file-upload.s3.amazonaws.com/web/direct-files/attachments/images/139277961/b869cfc5-946a-439c-8dea-ffe43541c815/image.jpg)
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.