SDDM does not display/no signal after adding new monitor

I just got myself a new monitor and now have trouble with SDDM. Previous setup was a Dell U2417H connected via DP to my desktop PC. Everything was working fine. New monitor is a Dell P2423DE connected via DP to my PC. The other Dell is now daisy chained. When I boot I can see the UEFI/Bios screen and the systemd-boot menu. After that I see some kernel messages since I had to disable the splash boot option due to a bug in Neon. After that usually SDDM would come up but now all I’m getting is “no Signal” and my monitor going into standby. I have tried just typing in my password and hitting enter but without success. As soon as I switch to a different tty my monitor wakes up. I can login there and start a plasma session with dbus-run-session startplasma-wayland. I have gone into system settings and applied Plasma settings to SDDM after setting up my monitors properly. That didn’t help. System details below. Can anyone help?

Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.8.0-49-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15,6 GiB of RAM
Graphics Processor: AMD Radeon RX 5500 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B550 AORUS PRO

Hi - it might be worth checking if there any messages in the system journal (you could use sudo journalctl --boot=0 to look at messages from the current system boot), from right around the time that SDDM fails to display, that give any clues?

And just checking, does the issue occur if you disconnect the daisy-chained monitor? How about if you connect both monitors directly to the graphics card (perhaps there’s something in the daisy-chaining somehow)?

Thanks. Daisy chaining does not seem to be the issue, it even happens with the second monitor turned off. Also weirdly sddm runs just fine when I restart it in tty.

journalctl:

SDDM with problems - Pastebin.com is what I get now

sddm before problems - Pastebin.com how it was before the new monitor = before the problem started

Seems like the screen size is not detected properly (line 44 in with problems)?

I’m definitely not a graphics expert so this likely needs a smarter person than I am to look at…

The only other thing that jumped out at me between the two was, did assigning Breeze as the SDDM theme coincide with the issue starting, or did the issue start before you changed the theme? (Just wondering if somehow something loosely related to 494804 – With Qt 6.8 controls to log in or unlock screen are non-functional on some monitors when using the Breeze SDDM or Plasma theme ("TypeError: [thing] is not a function" error) could be impacting here)

switching to Breeze was something I tried after the problem started to make sure it was not the custom theme causing issues.

Fixed by configuring SDDM to use Wayland instead of X: SDDM - ArchWiki