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.
sddm fails to start with vfio-pci GPU active
Reported by madebynoxc · filed Oct 22, 2025Closed upstream on 2025-10-28 by its own reporter madebynoxc. GitHub close reason: completed. 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
System details
Radeon RX 580 (main), Radeon RX 6750 XT (passthough), Omarchy 3.1.1
What's wrong?
I have a 2-GPU setup with KVM where I pass though one of the GPUs. Everything worked fine on Omarchy 3.0, and after I updated to 3.1.1 the screen was black after putting in my password, and from journalctl I could see that sddm has issues during startup:
sddm[2008]: Initializing...
sddm[2008]: Starting...
sddm[2008]: Logind interface found
sddm[2008]: Adding new display...
sddm[2008]: Loaded empty theme configuration
sddm[2008]: Xauthority path: "/run/sddm/xauth_BiUFEx"
sddm[2008]: Using VT 2
sddm[2008]: Display server starting...
sddm[2008]: Writing cookie to "/run/sddm/xauth_BiUFEx"
sddm[2008]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_BiUFEx -noreset -displayfd 16
sddm[2008]: Failed to read display number from pipe
sddm[2008]: Display server stopping...
sddm[2008]: Attempt 1 starting the Display server on vt 2 failed
sddm[2008]: Display server starting...
sddm[2008]: Writing cookie to "/run/sddm/xauth_BiUFEx"
sddm[2008]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_BiUFEx -noreset -displayfd 16
sddm[2008]: Failed to read display number from pipe
sddm[2008]: Display server stopping...
sddm[2008]: Attempt 2 starting the Display server on vt 2 failed
sddm[2008]: Display server starting...
sddm[2008]: Writing cookie to "/run/sddm/xauth_BiUFEx"
sddm[2008]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_BiUFEx -noreset -displayfd 16
sddm[2008]: Failed to read display number from pipe
sddm[2008]: Display server stopping...
sddm[2008]: Attempt 3 starting the Display server on vt 2 failed
sddm[2008]: Could not start Display server on vt 2I managed to resolve this issue by removing the HDMI cable from my pass through GPU before turning on the computer. The KVM works fine if I connect the cable to the GPU after Omarchy startup.
However, I would like to avoid doing it every time, so I appreciate any potential fix for this setup.
Before Omarchy I also ran this setup on KDE Fedora that uses sddm, and it was working fine.
Here is an output for lspci -nnk for my GPUs:
0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] [1002:73df] (rev c0)
Subsystem: ASUSTeK Computer Inc. Device [1043:05e7]
Kernel driver in use: vfio-pci
Kernel modules: amdgpu
0a:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller [1002:ab28]
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller [1002:ab28]
Kernel driver in use: vfio-pci
Kernel modules: snd_hda_intel
04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7)
Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] [1002:aaf0]
Subsystem: Sapphire Technology Limited Device [1da2:aaf0]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intelView raw text
### System details Radeon RX 580 (main), Radeon RX 6750 XT (passthough), Omarchy 3.1.1 ### What's wrong? I have a 2-GPU setup with KVM where I pass though one of the GPUs. Everything worked fine on Omarchy 3.0, and after I updated to 3.1.1 the screen was black after putting in my password, and from journalctl I could see that sddm has issues during startup: ``` sddm[2008]: Initializing... sddm[2008]: Starting... sddm[2008]: Logind interface found sddm[2008]: Adding new display... sddm[2008]: Loaded empty theme configuration sddm[2008]: Xauthority path: "/run/sddm/xauth_BiUFEx" sddm[2008]: Using VT 2 sddm[2008]: Display server starting... sddm[2008]: Writing cookie to "/run/sddm/xauth_BiUFEx" sddm[2008]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_BiUFEx -noreset -displayfd 16 sddm[2008]: Failed to read display number from pipe sddm[2008]: Display server stopping... sddm[2008]: Attempt 1 starting the Display server on vt 2 failed sddm[2008]: Display server starting... sddm[2008]: Writing cookie to "/run/sddm/xauth_BiUFEx" sddm[2008]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_BiUFEx -noreset -displayfd 16 sddm[2008]: Failed to read display number from pipe sddm[2008]: Display server stopping... sddm[2008]: Attempt 2 starting the Display server on vt 2 failed sddm[2008]: Display server starting... sddm[2008]: Writing cookie to "/run/sddm/xauth_BiUFEx" sddm[2008]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_BiUFEx -noreset -displayfd 16 sddm[2008]: Failed to read display number from pipe sddm[2008]: Display server stopping... sddm[2008]: Attempt 3 starting the Display server on vt 2 failed sddm[2008]: Could not start Display server on vt 2 ``` I managed to resolve this issue by removing the HDMI cable from my pass through GPU before turning on the computer. The KVM works fine if I connect the cable to the GPU after Omarchy startup. However, I would like to avoid doing it every time, so I appreciate any potential fix for this setup. Before Omarchy I also ran this setup on KDE Fedora that uses sddm, and it was working fine. Here is an output for `lspci -nnk` for my GPUs: ``` 0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] [1002:73df] (rev c0) Subsystem: ASUSTeK Computer Inc. Device [1043:05e7] Kernel driver in use: vfio-pci Kernel modules: amdgpu 0a:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller [1002:ab28] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller [1002:ab28] Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel 04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] Kernel driver in use: amdgpu Kernel modules: amdgpu 04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] [1002:aaf0] Subsystem: Sapphire Technology Limited Device [1da2:aaf0] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ```
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.