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.
4K@120 HDMI screen blanks for seconds on every new frame after linux-omarchy 7.2.5-3 (AMD Navi 33)
Reported by berkesadam74 · filed Sep 16, 2026 · open at source
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
What happened
After today's omarchy update (Omarchy 4.0.3 → 4.0.4, which installed the new linux-omarchy 7.2.5-3 kernel and booted into it), my 4K monitor goes completely black for ~2–5 seconds and then comes back whenever the compositor draws a new frame after the screen has been static for a moment — e.g. every time I start typing, move the mouse after a pause, or a notification appears. It makes the desktop unusable.
Switching the monitor to 3840x2160@60 makes the problem disappear immediately. At 3840x2160@120 it blanks on almost every static→active transition.
What I expected
4K@120 over HDMI 2.1 worked fine before today's update on this same hardware, cable and monitor.
Steps to reproduce
- AMD RDNA3 GPU + HDMI 2.1 monitor at
3840x2160@120 - Update to Omarchy 4.0.4 / boot the
linux-omarchy 7.2.5-3kernel - Let the screen sit idle for a second, then type or move the mouse
- Screen blanks for a few seconds, then re-syncs
What I checked
- Hyprland VRR is off (
hyprctl monitors→vrr: false; config hadvrr = 2, also triedvrr = 0) — no change - FreeSync / Adaptive-Sync is off in the monitor OSD
- No DPMS event, no mode change, no
drm/amdgpumessage is logged in the Hyprland log orjournalctl -kwhile the blank happens — it looks like a silent HDMI link drop/re-sync - The only amdgpu warning at boot:
amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 150000 tries - optc32_disable_crtc line:196 - Workaround:
hl.monitor({ ..., mode = "3840x2160@60", vrr = 0 })in~/.config/hypr/monitors.lua— fully stable at 60 Hz
The stock linux 7.2.3.arch1-3 kernel is still installed; I haven't yet rebooted into it to confirm the regression is kernel-only — will update this issue once I have.
System
- Omarchy: 4.0.4-1
- Kernel:
linux-omarchy 7.2.5-3(built 2026-09-14), running7.2.5-3-omarchy - Previous kernel:
linux 7.2.3.arch1-3(Arch) - CPU: AMD Custom CPU 1772
- GPU: AMD Navi 33 [Radeon Graphics] (PCI 1002:7481, rev c7), amdgpu, DCN 3.2
- Monitor: Gigabyte M28U on
HDMI-A-1,3840x2160@120, scale 1.6 - Hyprland 0.56.2-2, aquamarine 0.15.0-2, mesa 26.2.2-1, linux-firmware-amdgpu 20260810-2
- Boot params: default Omarchy (limine, encrypted btrfs), no amdgpu options
View raw text
## What happened
After today's `omarchy update` (Omarchy 4.0.3 → 4.0.4, which installed the new `linux-omarchy 7.2.5-3` kernel and booted into it), my 4K monitor goes **completely black for ~2–5 seconds and then comes back** whenever the compositor draws a new frame after the screen has been static for a moment — e.g. every time I start typing, move the mouse after a pause, or a notification appears. It makes the desktop unusable.
Switching the monitor to **3840x2160@60** makes the problem disappear immediately. At **3840x2160@120** it blanks on almost every static→active transition.
## What I expected
4K@120 over HDMI 2.1 worked fine before today's update on this same hardware, cable and monitor.
## Steps to reproduce
1. AMD RDNA3 GPU + HDMI 2.1 monitor at `3840x2160@120`
2. Update to Omarchy 4.0.4 / boot the `linux-omarchy 7.2.5-3` kernel
3. Let the screen sit idle for a second, then type or move the mouse
4. Screen blanks for a few seconds, then re-syncs
## What I checked
- Hyprland VRR is off (`hyprctl monitors` → `vrr: false`; config had `vrr = 2`, also tried `vrr = 0`) — no change
- FreeSync / Adaptive-Sync is **off** in the monitor OSD
- No DPMS event, no mode change, no `drm`/`amdgpu` message is logged in the Hyprland log or `journalctl -k` while the blank happens — it looks like a silent HDMI link drop/re-sync
- The only amdgpu warning at boot: `amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 150000 tries - optc32_disable_crtc line:196`
- Workaround: `hl.monitor({ ..., mode = "3840x2160@60", vrr = 0 })` in `~/.config/hypr/monitors.lua` — fully stable at 60 Hz
The stock `linux 7.2.3.arch1-3` kernel is still installed; I haven't yet rebooted into it to confirm the regression is kernel-only — will update this issue once I have.
## System
- Omarchy: 4.0.4-1
- Kernel: `linux-omarchy 7.2.5-3` (built 2026-09-14), running `7.2.5-3-omarchy`
- Previous kernel: `linux 7.2.3.arch1-3` (Arch)
- CPU: AMD Custom CPU 1772
- GPU: AMD Navi 33 [Radeon Graphics] (PCI 1002:7481, rev c7), amdgpu, DCN 3.2
- Monitor: Gigabyte M28U on `HDMI-A-1`, `3840x2160@120`, scale 1.6
- Hyprland 0.56.2-2, aquamarine 0.15.0-2, mesa 26.2.2-1, linux-firmware-amdgpu 20260810-2
- Boot params: default Omarchy (limine, encrypted btrfs), no amdgpu options
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 14:04 UTC