Stop an external monitor going black every time the Display panel opens
Read /usr/share/omarchy/bin/omarchy-brightness-display-ddc on 4.0.4-1 and diffed it against quattro: identical. Confirmed every mechanism the cause names: the 60 s unavailable cache is written only when detect_bus finds no bus, read_brightness runs rm -f on the cache file when read_vcp fails, and find_bus returns 1 before calling ddcutil while now - stamp < 60, so a stamp of 9999999999 makes the negative entry permanent. Confirmed the Display panel path: shell/plugins/panels/monitor/Panel.qml and bin/omarchy-monitor-state both call omarchy-brightness-display --monitor. Issue #6855 is open and its comments contain the DDCRC_RETRIES line, the 48 to 50 s spacing, the empty-cache fingerprint, the silent journalctl -k, the multicoloured noise variant and the exact tmpfiles workaround. Confirmed on this workstation that the user systemd-tmpfiles-setup.service is disabled and is WantedBy=basic.target, so the enable step is needed. Not exercised: no ddcutil probe and no tmpfiles rule was applied here.
The entry disables DDC brightness for that connector name, not for that monitor. If a different monitor later gets the same name, for example after a dock replug renumbers the ports, its brightness keys and slider stop working too. Delete the .bus file and the tmpfiles line to undo it.
Symptom
Every time I open the display module in the bar, or run omarchy brightness display --monitor DP-1, that one external monitor goes completely black for two or three seconds and then comes back by itself. Nothing is changed on it. It happens on every open, not only the first. Some people see multicoloured pixel noise instead of black. It is common with a monitor behind a USB-C to HDMI adapter, or one that answers ddcutil detect but has no readable brightness. With the panel left open, the journal fills with lines like:
Error detecting VCP version using VCP feature xDF: DDCRC_RETRIES; EREMOTEIO(10)
roughly every 50 seconds, and journalctl -k shows nothing at all.
Cause
omarchy-brightness-display-ddc caches each connector's I2C bus in $XDG_RUNTIME_DIR/omarchy-brightness-display-ddc/<connector>.bus, so that the expensive ddcutil --skip-ddc-checks detect --brief scan runs only once. If the scan finds no monitor it writes an unavailable <timestamp> entry that holds for 60 seconds. The failing case takes a different path. When detect finds the monitor but getvcp 10 (brightness) fails, read_brightness runs rm -f "$cache_file" and keeps no record of the failure. So every later call, and the Display panel calls it each time it opens or refreshes, repeats the full detect scan, and that scan probes the DDC channel of every attached display. Some monitors, and some converters inside USB-C to HDMI cables, drop and retrain the link when probed, which is the blank. Because DDC/CI is I2C sideband traffic there is no modeset and no kernel log line. The rm -f branch is still present in 4.0.4-1 and on the quattro branch as of 2026-10-04, and the issue is open.
Fix
**Confirm it is this path.** Replace DP-2 with the monitor that blanks (hyprctl monitors | grep ^Monitor):
omarchy-brightness-display --monitor DP-2; echo "exit=$?"
ls -la "$XDG_RUNTIME_DIR/omarchy-brightness-display-ddc/"
If the command exits 1 and the directory has no DP-2.bus entry, this is the bug.
**Workaround (Omarchy 4): write the negative verdict the script does not keep.** The cache check treats an entry as fresh while now - stamp < 60, so a far-future stamp makes it permanent and the helper returns before it ever calls ddcutil:
mkdir -p "$XDG_RUNTIME_DIR/omarchy-brightness-display-ddc"
echo "unavailable 9999999999" > "$XDG_RUNTIME_DIR/omarchy-brightness-display-ddc/DP-2.bus"
$XDG_RUNTIME_DIR is a tmpfs that is emptied at logout, so to keep it across sessions use a user tmpfiles rule:
# ~/.config/user-tmpfiles.d/omarchy-ddc-skip.conf
d %t/omarchy-brightness-display-ddc 0755 - - -
f+ %t/omarchy-brightness-display-ddc/DP-2.bus 0644 - - - unavailable 9999999999
The user unit that applies these rules is disabled on Omarchy 4 (checked on 4.0.4-1), so enable it:
systemctl --user enable systemd-tmpfiles-setup.service
systemd-tmpfiles --user --create
This gives up DDC brightness on that connector. On the monitors this bug hits, the brightness read was already failing, so nothing that worked is lost.
Verify
Open and close the Display panel several times. The monitor no longer blanks. cat "$XDG_RUNTIME_DIR/omarchy-brightness-display-ddc/DP-2.bus" prints unavailable 9999999999, and journalctl --user -b | grep -c DDCRC_RETRIES stops climbing.