Created attachment 146795 [details] Crash log Changing configuration of multi-monitors crashes plasma in Wayland. STEPS TO REPRODUCE 1. Using Wayland session 2. Try to change configuration of multi-monitor setup either from keyboard shortcut or from 'Display Configuration'. OBSERVED RESULT Cursor blinked for couple seconds on both displays and then blank screen but Krunner is still accessible and plasma cane manually started. Restarting the plasma manually does not switch on or off the display. EXPECTED RESULT Changing the configuration; for e.g successfully extending current active monitor or turning off any monitor(internal or external). SOFTWARE/OS VERSIONS Endeavour OS Kernel:- 5.16.9(Zen) (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91 Qt Version: 5.15.2 ADDITIONAL INFORMATION My laptop only have Type C ports for video outputs. I have attached an Journalctl log of crash, hope it is helpful.
Can you get the backtrace of the crash? coredumpctl list kwin_wayland and put pid of the relevant crash in coredumpctl gdb <pid>, then type "bt"
Created attachment 146802 [details] Kwin Wayland GDB GDB crash log for kwin_wayland
(In reply to Vlad Zahorodnii from comment #1) > Can you get the backtrace of the crash? > > coredumpctl list kwin_wayland > > and put pid of the relevant crash in coredumpctl gdb <pid>, then type "bt" Hi, I Don't know how to do that on Arch and KDE debug guide says it may not be possible(on Arch) but I tried to follow the kwin debug guide and attached a GDB crash log not sure if this is what you want, I'm very novice in debugging KDE.
(In reply to Gurpreet Singh from comment #3) > (In reply to Vlad Zahorodnii from comment #1) > > Can you get the backtrace of the crash? > > > > coredumpctl list kwin_wayland > > > > and put pid of the relevant crash in coredumpctl gdb <pid>, then type "bt" > > Hi, I Don't know how to do that on Arch and KDE debug guide says it may not > be possible(on Arch) but I tried to follow the kwin debug guide and attached > a GDB crash log not sure if this is what you want, I'm very novice in > debugging KDE. can you install debuginfod, reboot your computer and try again? https://archlinux.org/news/debug-packages-and-debuginfod/
Created attachment 146805 [details] coredump-bt
(In reply to Vlad Zahorodnii from comment #4) > (In reply to Gurpreet Singh from comment #3) > > (In reply to Vlad Zahorodnii from comment #1) > > > Can you get the backtrace of the crash? > > > > > > coredumpctl list kwin_wayland > > > > > > and put pid of the relevant crash in coredumpctl gdb <pid>, then type "bt" > > > > Hi, I Don't know how to do that on Arch and KDE debug guide says it may not > > be possible(on Arch) but I tried to follow the kwin debug guide and attached > > a GDB crash log not sure if this is what you want, I'm very novice in > > debugging KDE. > > can you install debuginfod, reboot your computer and try again? > https://archlinux.org/news/debug-packages-and-debuginfod/ I have attached the coredumpctl gdb bt of PID(kwin_wayland)
Git commit e9db27d05d7b76c8a4fc12a6f5c059680917052f by Xaver Hugl. Committed on 18/02/2022 at 17:13. Pushed by zamundaaa into branch 'master'. backends/drm: ignore enabled state of outputs for the lifetime of layers A buffer is needed for atomic tests before the output is actually enabled Related: bug 450501 M +2 -2 src/backends/drm/egl_gbm_backend.cpp https://invent.kde.org/plasma/kwin/commit/e9db27d05d7b76c8a4fc12a6f5c059680917052f
Git commit 29bc1173c70b2a31753c791aa60fb33ee320440a by Xaver Hugl. Committed on 18/02/2022 at 19:50. Pushed by zamundaaa into branch 'Plasma/5.24'. backends/drm: ignore enabled state of outputs for the lifetime of surfaces A buffer is needed for atomic tests before the output is actually enabled Related: bug 450501 (cherry picked from commit e9db27d05d7b76c8a4fc12a6f5c059680917052f) M +8 -7 src/backends/drm/egl_gbm_backend.cpp M +2 -2 src/backends/drm/egl_gbm_backend.h https://invent.kde.org/plasma/kwin/commit/29bc1173c70b2a31753c791aa60fb33ee320440a
Fixed in 5.24.2, Thank you.