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.
Hyprland failing to start when using a 4k 240hz monitor along with 3 other displays.
Reported by dmitrylito · filed May 7, 2026Closed upstream on 2026-05-07 by commit 4eb3a9198d53 (closed by dhh). GitHub close reason: completed.
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
AMD 9850 X3D, Nvidia 5080, LG ULTRAGEAR+ 32GX870A-B
What's wrong?
Detailed Fix: SDDM X11 Initialization Failure on High-End Nvidia Systems
1. The Core Issue
On systems with high-refresh rate 4K monitors (e.g., 240Hz) and Nvidia GPUs, the default SDDM configuration often fails to start. This results in a persistent black screen immediately after the boot splash (Plymouth) finishes.
2. Root Cause Breakdown
Investigation of the system logs (journalctl and /var/log/Xorg.0.log.old) revealed that SDDM's dependency on X11 for the login screen is the bottleneck:
- X11 Mode Validation Failure: During early boot, the Nvidia driver fails to validate the high-bandwidth display modes required for 4K @ 240Hz when requested by the X server.
- Log Evidence:
(EE) NVIDIA(0): Unable to use default mode "nvidia-auto-select".(EE) Screen(s) found, but none have a usable configuration.Fatal server error: no screens found- SDDM Timeout: SDDM attempts to launch this X server three times. After the third failure, it gives up entirely. Because the greeter never loads, the autologin process to Hyprland never triggers, leaving the user at a black screen.
3. The Definitive Solution: SDDM in Wayland Mode
The fix is to bypass the buggy X11 initialization entirely by forcing SDDM to use a Wayland-based greeter. Since the system is already running Hyprland, we can use Hyprland as the compositor for the SDDM login screen.
Implementation Steps:
- Created a drop-in configuration file:
/etc/sddm.conf.d/10-wayland.conf - Applied the following settings:
[General]
DisplayServer=wayland
[Wayland]
CompositorCommand=hyprlandWhy This Works:
By switching the DisplayServer to wayland, SDDM no longer tries to start an X server. It instead uses Hyprland to manage the display, which handles modern Nvidia handshakes and high-refresh 4K modes much more reliably than the legacy Xorg server.
View raw text
### System details
AMD 9850 X3D, Nvidia 5080, LG ULTRAGEAR+ 32GX870A-B
### What's wrong?
# Detailed Fix: SDDM X11 Initialization Failure on High-End Nvidia Systems
## 1. The Core Issue
On systems with high-refresh rate 4K monitors (e.g., 240Hz) and Nvidia GPUs, the default SDDM configuration often fails to start. This results in a persistent black screen immediately after the boot splash (Plymouth) finishes.
## 2. Root Cause Breakdown
Investigation of the system logs (`journalctl` and `/var/log/Xorg.0.log.old`) revealed that **SDDM's dependency on X11 for the login screen** is the bottleneck:
* **X11 Mode Validation Failure**: During early boot, the Nvidia driver fails to validate the high-bandwidth display modes required for 4K @ 240Hz when requested by the X server.
* **Log Evidence**:
- `(EE) NVIDIA(0): Unable to use default mode "nvidia-auto-select".`
- `(EE) Screen(s) found, but none have a usable configuration.`
- `Fatal server error: no screens found`
* **SDDM Timeout**: SDDM attempts to launch this X server three times. After the third failure, it gives up entirely. Because the greeter never loads, the autologin process to Hyprland never triggers, leaving the user at a black screen.
## 3. The Definitive Solution: SDDM in Wayland Mode
The fix is to bypass the buggy X11 initialization entirely by forcing SDDM to use a Wayland-based greeter. Since the system is already running Hyprland, we can use Hyprland as the compositor for the SDDM login screen.
### Implementation Steps:
1. Created a drop-in configuration file: `/etc/sddm.conf.d/10-wayland.conf`
2. Applied the following settings:
```ini
[General]
DisplayServer=wayland
[Wayland]
CompositorCommand=hyprland
```
### Why This Works:
By switching the `DisplayServer` to `wayland`, SDDM no longer tries to start an X server. It instead uses Hyprland to manage the display, which handles modern Nvidia handshakes and high-refresh 4K modes much more reliably than the legacy Xorg server.
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.