SUMMARY KWin_wayland segfaults when any monitor is disconnected, such as when my LG 24UD58-B goes into DPMS power save mode when the screen saver activates. It reconnects itself when DPMS re-powered. STEPS TO REPRODUCE 1. Log into Plasma Wayland session. 2. Lock the screen and wait for the screen saver to power the monitors off. 3. Wake the desktop and unlock the screen. OBSERVED RESULT Kwin crashes, and the session is restored from scratch. EXPECTED RESULT The session continues unabated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.11.0-122 (available in About System) KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION kwin_wayland produced an absolutely useless backtrace log.
Created attachment 136024 [details] Backtrace
I am experiencing the same issue intermittently, and with some differences the rest of the time. I have a DisplyPort and USB3 switch (poor man's KVM) that I use to switch between my work and Linux PCs. When switching away and back to my Linux machine running Plasma Wayland, one of the following things happens in order of most to least often: 1. My desktop is available, but the panel is missing most of the icons and widgets, and attempts to interact with it do nothing. There are other artifacts on existing window borders as well, but most of the applications are still available if they were already running. I can restore most of desktop functionality by running these commands: `kquitapp5 plasmashell ; kstart5 plasmashell` 2. The display has nothing but scattered, glitchy fragments of my last session, and cannot be interacted with at all. Switching TTYs and running `loginctl unlock-session x` will usually get me back to the first state. 3. I get a black screen with text telling me that I need to run loginctl from another TTY, which works and gives me the 1st state. 4. The display gets no signal at all, as though my machine was completely locked up or powered down. I can usually switch to another TTY, though it takes ~20 seconds for the display to awaken, and I have to completely restart sddm and lose my session to get graphics back. Switching to a text TTY and back to where the graphical session was without restarting sddm causes the display to immediately lose signal, and another ~20 second wait to get back to a text TTY. 5. My system is completely unresponsive and a hard reset is needed. I haven't had this happen since 5.21 was released, but it did rarely occur in the last couple releases. My system info: Operating System: Arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-zen1-1-zen OS Type: 64-bit Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT
According to the backtrace, plasmashell crashed, not kwin_wayland.
Which could be as a result of kwin crashing, but we still can't do much without the kwin backtrace.
I may as well close this, then. My distribution doesn't provide debugging symbols, so the entire backtrace is a single function call address and nothing else.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!