Created attachment 179842 [details] Crash dump text SUMMARY I have a monitor setup with two monitors connected via a Display Port daisy chain. I can enable / disable the MST option on the first monitor to treat them either as one or two monitors. STEPS TO REPRODUCE 1. Running KDE plasma session on wayland 2. Enable MST OBSERVED RESULT Wayland crash. Screen is black with underscore character in topleft corner. Opening a console session works. System recovers after disabling MST. EXPECTED RESULT I can extend my screen to both monitors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 41 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION I sent an automatic crash report, but I can't find it .
#0 0x00007f16d907fb54 __pthread_kill_implementation (libc.so.6 + 0x72b54) #1 0x00007f16d9026f9e raise (libc.so.6 + 0x19f9e) #2 0x00007f16dcb4e37e _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x537e) #3 0x00007f16d9027050 __restore_rt (libc.so.6 + 0x1a050) #4 0x00007f16dc5126b3 _ZN4KWin11DrmPipeline25prepareAtomicPresentationEPNS_15DrmAtomicCommitERKSt10shared_ptrINS_11OutputFrameEE (libkwin.so.6 + 0x3126b3) #5 0x00007f16dc514a38 _ZN4KWin11DrmPipeline7presentERKSt10shared_ptrINS_11OutputFrameEE (libkwin.so.6 + 0x314a38) #6 0x00007f16dc516832 _ZN4KWin9DrmOutput7presentERKSt10shared_ptrINS_11OutputFrameEE (libkwin.so.6 + 0x316832) #7 0x00007f16dc260f43 _ZN4KWin17WaylandCompositor9compositeEPNS_10RenderLoopE (libkwin.so.6 + 0x60f43) #8 0x00007f16d975a26e _Z10doActivateILb0EEvP7QObjectiPPv (libQt6Core.so.6 + 0x15a26e) #9 0x00007f16dc275af4 _ZN4KWin10RenderLoop14frameRequestedEPS0_ (libkwin.so.6 + 0x75af4) #10 0x00007f16dc27ab12 _ZN4KWin17RenderLoopPrivate8dispatchEv (libkwin.so.6 + 0x7ab12) #11 0x00007f16d975a26e _Z10doActivateILb0EEvP7QObjectiPPv (libQt6Core.so.6 + 0x15a26e) #12 0x00007f16d976a02d _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt6Core.so.6 + 0x16a02d) #13 0x00007f16d974b935 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x14b935) #14 0x00007f16da83d9b8 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x3d9b8) #15 0x00007f16d96f3590 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0xf3590) #16 0x00007f16d98b4e28 _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x2b4e28) #17 0x00007f16d98b929b _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2b929b) #18 0x00007f16da4cabf2 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x6cabf2) #19 0x00007f16d9700993 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x100993) #20 0x00007f16d96fbf6e _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0xfbf6e) #21 0x000055db23046786 main (kwin_wayland + 0xf786) #22 0x00007f16d9010248 __libc_start_call_main (libc.so.6 + 0x3248) #23 0x00007f16d901030b __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x330b) #24 0x000055db2304c9c5 _start (kwin_wayland + 0x159c5) Looks like it's the same thing as Bug 502156.
It's a bit difficult to tell if it's exactly the same thing. Please get me a complete backtrace ("coredumpctl debug kwin_wayland" and then "bt" in the gdb console), and attach the output of > journalctl --user-unit plasma-kwin_wayland --boot 0 after reproducing the crash.
Created attachment 180094 [details] sudo coredumpctl debug kwin_wayland
Created attachment 180095 [details] journalctl --user-unit plasma-kwin_wayland --boot 0
Hey, thanks for looking into it and I'm sorry for the delay.
*** This bug has been marked as a duplicate of bug 500031 ***