Created attachment 161827 [details] output of journalctl after the issue occurs On my laptop (Dell Latitude 7410, Intel Core i5-10310U CPU, Wayland) I often experience a crash of the screen locker when resuming from the sleep state. I then have to manually unlock the session in a tty using unlockctl. The crash seems to happen more or less randomly, although I have the suspicion that it happens mostly when a multi-monitor setup is involved (such as going into standby mode, then disconnecting from the docking station w and then waking up the battery-powered laptop again) I attached the relevant output of journalctl, looking forward to further ideas. This was first reported in https://bugs.kde.org/show_bug.cgi?id=374890#c53. As suggested by Nate, I opened this new bugreport.
Sep 21 08:01:27 latitude kernel: traps: kscreenlocker_g[14410] general protection fault ip:7f7f9c847de8 sp:7fff4bc6d988 error:0 in libQt5Qml.so.5.15.10[7f7f9c6a7000+281000] Well that doesn't seem good. There's also: Sep 21 08:01:27 latitude kscreenlocker_greet[14825]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 21 08:01:27 latitude kscreenlocker_greet[14825]: The Wayland connection experienced a fatal error: Das Argument ist ungültig ("Invalid argument" in English) Sep 21 08:01:27 latitude kscreenlocker_greet[14837]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 21 08:01:27 latitude kscreenlocker_greet[14837]: The Wayland connection broke. Did the Wayland compositor die? If you run `coredumpctl --reverse`, do you see any crashes in kwin_wayland, or kscreenlocker_greet in the first 10 or 15 entries? Does it ever happen with only a single screen connected?
coredumpctl --reverse shows some kwin_kwayland entries, but they are from two weeks ago, so that seems unrelated... It also happens when waking up in single-screen mode (no external devices connected), most commonly when I go to standby while still being connected to a docking station, then disconnect it while being in standby and waking it up in single-screen mode. I'm not sure if I have ever observed it when going into sleep from single-screen and waking up in single-screen, but I will try to reproduce this.
Thanks, the information provided that it often happens when the screen arrangement changed while asleep is helpful.
Given I also have these crashes on the same system where I get bug 467147, with the same log output, it will be related.
*** Bug 476334 has been marked as a duplicate of this bug. ***
Is there any chance that either of you can test this out in Plasma 6 (https://community.kde.org/Plasma/Plasma_6#How_to_use%2Ftest_it)? We've re-done a core part of how multi-monitor handling works on Wayland and are focusing on issues like this lately. I haven't been able to reproduce this issue myself when changing the screen arrangement while asleep. Would you be able to give it try sometime on Plasma 6? That would be very helpful! If you can still reproduce the crash, a backtrace of the crash in question would be helpful.
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!
(In reply to Nate Graham from comment #6) > Is there any chance that either of you can test this out in Plasma 6 > (https://community.kde.org/Plasma/Plasma_6#How_to_use%2Ftest_it)? We've > re-done a core part of how multi-monitor handling works on Wayland and are > focusing on issues like this lately. In my case it is not even multiscreen related. Lockscreen broke again with Plasma 5.91, and plasmashell currently crashes each time either on DP screen standby or wakeup. [ 1301.084024] QSGRenderThread[6426]: segfault at 7f1cbd209a00 ip 00007f1cbd209a00 sp 00007f1c6a7fc868 error 15 in libQt6Core.so.6.6.1[7f1cbd1e7000+1f2000] likely on CPU 14 (core 14, socket 0) [ 1301.084039] Code: 74 72 61 63 74 44 79 6e 61 6d 69 63 4d 65 74 61 4f 62 6a 65 63 74 00 00 00 00 51 4f 62 6a 65 63 74 00 00 00 00 00 00 00 00 00 <32> 31 51 4f 62 6a 65 63 74 43 6c 65 61 6e 75 70 48 61 6e 64 6c 65 [ 1302.721817] plasmashell[6573]: segfault at 5c ip 00007f9a511aa78b sp 00007ffcc51f6360 error 4 in libQt6Core.so.6.6.1[7f9a510b3000+334000] likely on CPU 15 (core 15, socket 0) [ 1302.721832] Code: 00 00 00 48 89 68 20 41 8b 54 24 54 81 e6 ff ff ff 07 89 f0 0d 00 00 00 40 81 e2 00 00 00 b8 09 d0 41 89 44 24 54 49 8b 45 08 <4c> 8b 78 58 4c 89 ff e8 c9 d0 09 00 4d 89 7c 24 30 4d 89 6c 24 28 Operating System: Gentoo 2.14 KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.5.11-gentoo (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Product Name: X570 Phantom Gaming-ITX/TB3
But did it break in the same way, or in a different way? I can't tell from that log what's going on. Can you attach a proper symbolicated backtrace?