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.
i915 driver: USB-C dock display fails to re-detect after unplug/replug (kernel 7.2.3 regression)
Reported by rrooding · filed Sep 25, 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
Summary
When a display is connected via a USB-C dock (Satechi) and then unplugged and reconnected, the Intel i915 GPU driver fails to re-detect the display. The display remains disconnected until the system is rebooted.
Hardware
- Omarchy Version: 4.0.4-1
- Kernel: 7.2.3.arch1-3
- Hyprland: 0.56.2-2
- Laptop: Omarchy running on Intel UHD Graphics (Raptor Lake-P)
- Dock: Satechi USB-C dongle
- Monitor: Dell P2417H (connected via HDMI through dongle)
Steps to Reproduce
- Connect a monitor via USB-C dock (e.g., Satechi dongle → HDMI)
- Verify monitor is working (
hyprctl monitors allshows it) - Unplug the USB-C dock
- Plug the USB-C dock back in
- Run
hyprctl monitors all— monitor is no longer detected
Expected Behavior
The display should be re-detected and become available in hyprctl monitors all
Actual Behavior
hyprctl monitors allshows only the laptop display (eDP-1)modetest -cshows all output ports (DP-1, DP-2, HDMI-A-1) as disconnected/sys/class/drm/card2-DP-1/statusreads "disconnected"/sys/class/drm/card2-DP-1/edidis empty (driver didn't read monitor EDID)- Running
hyprctl reloadhas no effect - Full system reboot is required to re-detect the display
Root Cause
This is a kernel/i915 driver issue, not Hyprland. Evidence:
- The i915 driver fails to detect the display at the DRM level (before Hyprland even loads)
- Even
modetest(a userspace tool that directly queries DRM) shows the display as disconnected - USB devices on the dock ARE re-detected (lsusb shows the Satechi USB hubs reconnecting)
- Only the display output is not re-detected
Workarounds Attempted
hyprctl reload— no effect- Manual
modetest -r— no effect - GPU power cycle via sysfs — no effect
- udev/systemd hotplug detection scripts — doesn't help (driver never detects)
- Reboot — WORKS
Timeline
This issue appeared after updating to kernel 7.2.3.arch1-3 and Hyprland 0.56.2-2 on September 9, 2026. It was working on previous kernel versions.
Notes
- This issue affects any USB-C/Thunderbolt docking station, not just Satechi
- Related issue: #13119 (AMD amdgpu USB-C dock issue on kernel 7.2.5)
- The underlying cause is that the Intel i915 driver doesn't trigger hotplug detection when displays are reconnected via USB-C docks
- This is likely a kernel or i915 driver regression, not an Omarchy issue, but it significantly impacts Omarchy users with USB-C docks
View raw text
## Summary When a display is connected via a USB-C dock (Satechi) and then unplugged and reconnected, the Intel i915 GPU driver fails to re-detect the display. The display remains disconnected until the system is rebooted. ## Hardware - **Omarchy Version:** 4.0.4-1 - **Kernel:** 7.2.3.arch1-3 - **Hyprland:** 0.56.2-2 - **Laptop:** Omarchy running on Intel UHD Graphics (Raptor Lake-P) - **Dock:** Satechi USB-C dongle - **Monitor:** Dell P2417H (connected via HDMI through dongle) ## Steps to Reproduce 1. Connect a monitor via USB-C dock (e.g., Satechi dongle → HDMI) 2. Verify monitor is working (`hyprctl monitors all` shows it) 3. Unplug the USB-C dock 4. Plug the USB-C dock back in 5. Run `hyprctl monitors all` — monitor is no longer detected ## Expected Behavior The display should be re-detected and become available in `hyprctl monitors all` ## Actual Behavior - `hyprctl monitors all` shows only the laptop display (eDP-1) - `modetest -c` shows all output ports (DP-1, DP-2, HDMI-A-1) as disconnected - `/sys/class/drm/card2-DP-1/status` reads "disconnected" - `/sys/class/drm/card2-DP-1/edid` is empty (driver didn't read monitor EDID) - Running `hyprctl reload` has no effect - Full system reboot is required to re-detect the display ## Root Cause This is a **kernel/i915 driver issue**, not Hyprland. Evidence: - The i915 driver fails to detect the display at the DRM level (before Hyprland even loads) - Even `modetest` (a userspace tool that directly queries DRM) shows the display as disconnected - USB devices on the dock ARE re-detected (lsusb shows the Satechi USB hubs reconnecting) - Only the display output is not re-detected ## Workarounds Attempted - `hyprctl reload` — no effect - Manual `modetest -r` — no effect - GPU power cycle via sysfs — no effect - udev/systemd hotplug detection scripts — doesn't help (driver never detects) - Reboot — **WORKS** ## Timeline This issue appeared after updating to kernel 7.2.3.arch1-3 and Hyprland 0.56.2-2 on September 9, 2026. It was working on previous kernel versions. ## Notes - This issue affects any USB-C/Thunderbolt docking station, not just Satechi - Related issue: #13119 (AMD amdgpu USB-C dock issue on kernel 7.2.5) - The underlying cause is that the Intel i915 driver doesn't trigger hotplug detection when displays are reconnected via USB-C docks - This is likely a kernel or i915 driver regression, not an Omarchy issue, but it significantly impacts Omarchy users with USB-C docks
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 19:43 UTC