Wayland/KDE session crashes on startup (dual monitor)

[marcusdaheim]

Hi All!
Updated the system (KDE Plasma 6.3.2, Kernel 6.13.5-arch1-1 (64-bit)) and rebooted as suggested on March 2, since then Wayland/KDE doesn’t start up in dual monitor configuration anymore. Single monitor configuration works fine, as well as fallback to X11 with dual monitor. HW is a Lenovo T420 with Intel HD Graphics 3000.
Would love to stick with Wayland but for now am forced to use X11.
Any idea?
Edit: Was able to replicate the issue by creating a new test user account, so it’s a system-wide issue and not limited to one user.

[Bink]

Welcome to the community @marcusdaheim

@marcusdaheim

since then Wayland/KDE doesn’t start up in dual monitor configuration anymore. Single monitor configuration works fine, as well as fallback to X11 with dual monitor.

Would you be able to clarify please, what you mean when you say it “doesn’t start up”? With two dual monitors running, what stages do you see / not see, as the system starts up?

Some detailed system information may also highlight something:

inxi -Fxx --za | eos-sendlog

[marcusdaheim]

Thanks for your reply!
Link to the log: https://0x0.st/8Mf7.txt
To detail what I see:

• System boots up into sddm
• Pick UID and enter PW, login. Plasma (Wayland) is selected as the WM.
• Screen turns dark, no KDE greeter. Sometimes the mouse cursor is visible.
• No further activity, systems remains in that state (for at least 30min - tested).
• This only happens when an external monitor is attached to the laptop. No external monitor and KDE starts as expected. External monitor is connected via Display Port (maybe I can try VGA and see if this makes a difference).
• I can, however, open a tty session and see in btop that some KDE processes have started. That tells me that the system itself is running and only KDE didn’t complete its startup sequence. No excessive system load or run-away memory usage. I am able to shutdown/reboot the system from the command prompt.
• Furthermore, I created a fresh user profile which shows exactly the same behavior, ruling out that this issue is connected to the UID.
• Choosing Plasma(X11) as a WM and everything works as expected. For now, I’m using X11 as a fallback and all is working fine.
  Hope this info helps! If you need more detailed info (logs), let me know!
  Thanks, Marcus