Created attachment 176184 [details] konsole backtrace SUMMARY Maybe the connector of my non-MST display got loose, thus kwin switched to the previously turned off display (first in a MST chain), upon discovering the display again, it switched the configuration back and I find crash notifications for kwrite and konsole. In the journal I see: Nov 28 12:30:26 <> kwalletd6[1836]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash and lots of firefox warnings: Couldn't map window 0x7a02a7ff27a0 as subsurface because its parent is not mapped. then Nov 28 12:31:48 <> kwin_wayland_wrapper[1976]: XWAYLAND: mode -1x-1 is not available Nov 28 12:31:48 <> kwin_wayland_wrapper[1976]: XWAYLAND: mode -1x-1 is not available Nov 28 12:31:48 <> kwin_wayland_wrapper[1976]: XWAYLAND: mode -1x-1 is not available Nov 28 12:31:48 <> kwin_wayland_wrapper[1976]: XWAYLAND: mode -1x-1 is not available STEPS TO REPRODUCE 1. have screens appear/disappear 2. crash if lucky OBSERVED RESULT konsole and kwrite crash EXPECTED RESULT they don't SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.12.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics Memory: 46.3 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION
Clients crashing is not a kwin bug, but a Qt bug. QWindowSystemInterface::handleScreenRemoved is the relevant part, we can track it in Qt