https://bugs.kde.org/show_bug.cgi?id=512146

--- Comment #2 from Lemma <[email protected]> ---
Summary:
On Fedora 43 (KDE Plasma 6.5.2), booting into the default Wayland session
(SDDM) results in a monitor "Out of Range" signal. This occurs on older Intel
Ivy Bridge hardware using a VGA connection. The issue is specific to Wayland;
forcing an X11 session for SDDM resolves the issue.
System Information
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.18
Qt Version: 6.10
Graphics Platform: Wayland (Default)
Processors: Intel Core i5-3470 (Ivy Bridge)
GPU: Intel HD Graphics 2500 (Integrated)
Monitor: Standard VGA Monitor (Max Resolution: 1024x768 @ 60Hz)
Connection Type: VGA (Analog)

note: i face same issue in ubuntu with older version of kde

Description:
After a fresh installation or update to Fedora 43, the system boots past the
BIOS and GRUB. When the boot sequence hands off to the Display Manager (SDDM),
the monitor goes black and displays a hardware-level "Out of Range" error
message.
This indicates that KWin/Wayland is attempting to drive the VGA monitor at a
refresh rate or resolution unsupported by the hardware (likely attempting 75Hz+
on a 60Hz-only panel), whereas X11 correctly identifies the safe limits.

Steps to Reproduce:
Install Fedora 43 KDE Spin on a system with Intel Ivy Bridge iGPU and a VGA
monitor (1024x768 native).
Ensure the system defaults to Wayland for SDDM (standard behavior).
Boot the computer.
Wait for the graphical login screen to load.
Observed Result
The monitor displays an "Out of Range" error message. No graphical interface is
visible. TTY switching (Ctrl+Alt+F3) is required to regain control.
Expected Result
The SDDM login screen should appear at the monitor's native resolution
(1024x768 @ 60Hz).

Workaround Verified:
The following actions resolve the issue, confirming it is a mode-setting
negotiation error in Wayland:
Forcing X11: Configuring /etc/sddm.conf.d/ with DisplayServer=x11 allows the
login screen to load correctly.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to