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.
linux-omarchy 7.2.5: external monitors on Thunderbolt/MST dock get wrong EDID or fail to modeset (Panther Lake, upstream xe regression)
Reported by DanielHartl · filed Sep 26, 2026Closed upstream on 2026-09-28 by its own reporter DanielHartl, as not planned. Closed by its own reporter — not by itself 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
Summary
linux-omarchy 7.2.5-3 (and stock Arch linux 7.2.3) corrupt the EDIDs of monitors that are connected through a Thunderbolt dock over DP MST, on Panther Lake (xe). The result is wrong monitor names and resolutions, and after a dock hotplug every modeset fails with -EINVAL, so the external monitors stay dark. Kernel 7.1 (linux-ptl 7.1.8) works correctly on the same hardware.
This is an upstream kernel regression (7.1 → 7.2), reported to the xe driver here with EDID dumps from both kernels:
https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/9421
I'm filing it here because linux-omarchy became the default boot entry (migration 1789325478), so affected users on Panther Lake with MST docks get this without having changed anything.
System
- Omarchy 4.0.4-1, Hyprland 0.56.2, aquamarine 0.15.0
- Dell laptop, Intel Panther Lake, Arc B390
[8086:b080], driverxe - Lenovo ThinkPad Thunderbolt 3 Dock, 3 monitors (HP 27ea 1080p, 2x Lenovo P27h-10 1440p)
Symptoms
- One monitor reports another monitor's EDID (identical name and serial), so
mode = "preferred"picks 1920x1080 on a 2560x1440 panel. Power-cycling the monitor does not help. - After the dock re-enumerates:
atomic drm request: failed to commit: Invalid argumentfor every mode, and the monitors stay at0x0.
Workaround
Boot a 7.1 kernel. Here, linux-ptl is first in BOOT_ORDER in /etc/default/limine, followed by limine-update.
View raw text
## Summary `linux-omarchy` 7.2.5-3 (and stock Arch `linux` 7.2.3) corrupt the EDIDs of monitors that are connected through a Thunderbolt dock over DP MST, on Panther Lake (`xe`). The result is wrong monitor names and resolutions, and after a dock hotplug every modeset fails with `-EINVAL`, so the external monitors stay dark. Kernel 7.1 (`linux-ptl` 7.1.8) works correctly on the same hardware. This is an upstream kernel regression (7.1 → 7.2), reported to the xe driver here with EDID dumps from both kernels: **https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/9421** I'm filing it here because `linux-omarchy` became the default boot entry (migration `1789325478`), so affected users on Panther Lake with MST docks get this without having changed anything. ## System - Omarchy 4.0.4-1, Hyprland 0.56.2, aquamarine 0.15.0 - Dell laptop, Intel Panther Lake, Arc B390 `[8086:b080]`, driver `xe` - Lenovo ThinkPad Thunderbolt 3 Dock, 3 monitors (HP 27ea 1080p, 2x Lenovo P27h-10 1440p) ## Symptoms - One monitor reports another monitor's EDID (identical name and serial), so `mode = "preferred"` picks 1920x1080 on a 2560x1440 panel. Power-cycling the monitor does not help. - After the dock re-enumerates: `atomic drm request: failed to commit: Invalid argument` for every mode, and the monitors stay at `0x0`. ## Workaround Boot a 7.1 kernel. Here, `linux-ptl` is first in `BOOT_ORDER` in `/etc/default/limine`, followed by `limine-update`.
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.