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

External display hot-plug leaves Intel outputs at 0x0 after dock reconnect

Reported by zairramirez · filed Sep 20, 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

External display hot-plug leaves Intel outputs at 0x0 after dock reconnectrevision 1 · captured 2026-09-28 21:23 UTC via poll

Description

External displays stop producing video after disconnecting and reconnecting a Dell docking station while the session is running. The same dock works with another Windows computer. If the laptop is rebooted with the dock already connected, the external displays work again.

The issue also occurs when connecting a Dell monitor directly to the laptop HDMI port, so it is not limited to the dock's MST path.

Steps to reproduce

  1. Boot the laptop with the Dell dock connected, or connect the dock and reboot.
  2. Confirm that the external Dell monitor(s) display correctly.
  3. Disconnect the dock from the laptop.
  4. Reconnect the dock without rebooting.
  5. The monitor is detected, but remains black.
  6. Connecting one monitor directly through HDMI produces the same behavior after a reconnect.

Expected behavior

The external display should be re-enabled and show the desktop after reconnecting the dock or HDMI cable.

Actual behavior

Hyprland detects the output as connected and reads its EDID and available modes, but the active mode is 0x0@60 and no image is displayed. Rebooting with the dock connected restores video.

System information

  • Omarchy: 4.0.4-1
  • Kernel: 7.2.5-3-omarchy
  • GPU: Intel Kaby Lake-R UHD Graphics 620 (8086:5917)
  • Driver: i915
  • Compositor: Hyprland 0.56.2
  • Dock USB devices identify as Dell/Realtek dock devices (413c:b06e, 413c:b06f, 0bda:5487, 0bda:5413, 0bda:0487, 0bda:0413)
  • Displays: Dell DELL S2421HGF, 1920x1080

Relevant logs

i915 0000:00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
i915 0000:00:02.0: [drm] *ERROR* Failed to get ACT after 3000 ms, last status: 00
EDID block 0 (tag 0x00) checksum is invalid, remainder is 33

The monitor connector is reported by the kernel as connected and exposes 1920x1080 modes, but Hyprland reports 0x0@60 for the output.

Workarounds tried

  • Removed the hyprmoncfg-bin monitor profile manager and returned monitor control to Hyprland/Omarchy.
  • Tested with both monitors, then with only one monitor connected to the dock.
  • Tested a monitor directly through the laptop HDMI port.
  • Reloaded Hyprland and attempted to force 1920x1080@60.
  • Power-cycled the dock.

None restored video without rebooting.

View raw text
## Description

External displays stop producing video after disconnecting and reconnecting a Dell docking station while the session is running. The same dock works with another Windows computer. If the laptop is rebooted with the dock already connected, the external displays work again.

The issue also occurs when connecting a Dell monitor directly to the laptop HDMI port, so it is not limited to the dock's MST path.

## Steps to reproduce

1. Boot the laptop with the Dell dock connected, or connect the dock and reboot.
2. Confirm that the external Dell monitor(s) display correctly.
3. Disconnect the dock from the laptop.
4. Reconnect the dock without rebooting.
5. The monitor is detected, but remains black.
6. Connecting one monitor directly through HDMI produces the same behavior after a reconnect.

## Expected behavior

The external display should be re-enabled and show the desktop after reconnecting the dock or HDMI cable.

## Actual behavior

Hyprland detects the output as connected and reads its EDID and available modes, but the active mode is `0x0@60` and no image is displayed. Rebooting with the dock connected restores video.

## System information

- Omarchy: `4.0.4-1`
- Kernel: `7.2.5-3-omarchy`
- GPU: Intel Kaby Lake-R UHD Graphics 620 (`8086:5917`)
- Driver: `i915`
- Compositor: Hyprland `0.56.2`
- Dock USB devices identify as Dell/Realtek dock devices (`413c:b06e`, `413c:b06f`, `0bda:5487`, `0bda:5413`, `0bda:0487`, `0bda:0413`)
- Displays: Dell DELL S2421HGF, 1920x1080

## Relevant logs

```text
i915 0000:00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
i915 0000:00:02.0: [drm] *ERROR* Failed to get ACT after 3000 ms, last status: 00
EDID block 0 (tag 0x00) checksum is invalid, remainder is 33
```

The monitor connector is reported by the kernel as `connected` and exposes 1920x1080 modes, but Hyprland reports `0x0@60` for the output.

## Workarounds tried

- Removed the `hyprmoncfg-bin` monitor profile manager and returned monitor control to Hyprland/Omarchy.
- Tested with both monitors, then with only one monitor connected to the dock.
- Tested a monitor directly through the laptop HDMI port.
- Reloaded Hyprland and attempted to force 1920x1080@60.
- Power-cycled the dock.

None restored video without rebooting.

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 16:52 UTC