Bug 450069

Summary: Plasma 5.24 freezes/black screen on wake from sleep
Product: [Plasma] kwin Reporter: ganthony.nuarin
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: major CC: kde, mesinodd, mistry01, nate, richts, semen.vozhov
Priority: NOR Keywords: regression
Version: 5.24.4   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: stacktrace from systemd-coredump
attachment-9790-0.html

Description ganthony.nuarin 2022-02-12 07:15:21 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Press powerbutton or systemctl suspend
2. Wait for the light indicator to blink indicating it's on sleep
3. Wake the by keyboard keys/power button

OBSERVED RESULT
The desktop is frozen in its current frame before sleep, or black if the black fade effect when sleeping takes effect sometimes. The cursor can still be moved although I cannot interact with the elements/icons or even start the terminal or ksysguard using meta+esc. I think its not the xserver as ctrl+alt+backspace still kills the desktop. I cannot diagnose any further as I don't have any further knowledge in reading logs. 

EXPECTED RESULT
To wake just fine and 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux 5.16.8

KDE Plasma Version: 5.24
KDE Frameworks Version: the latest ones 
Qt Version:  the latest ones

ADDITIONAL INFORMATION
Searching the web, this was a quite prevalent issue among users. 
As for me, I never encountered this before, just on Plasma 5.24.

I tried creating a new user using useradd and # startx from it and the bug still persists so I don't think it's some broken config files or plasmoids, I also don't have a dedicated GPU. Just integrated ones of i5 4210U. The only workaround I tried is diabling TLP, reenabling masked services, removing i915 and processor related kernel parameters and rebooting countless of times. They didn't work.

I also don't have a graphical login program like sddm and starts kde using startx. S3 power state is availabe, but I can't disable it in my bios... but it works in the past versions. My session files and xorg configs are okay i think and the rest of my setup is pretty standard. I'm on x11.

Also, if I switch to another TTY using ctrl+alt+f2 and did the suspended there either using systemctl or powerbutton (my logind.conf is set to suspend on button press) then woke the PC then switched to the tty with plasma on it, the screen is not frozen and i can interact with the icons. I also have i3wm installed and this doesn't happen to it during sleep.

After spending the night searching for a fix, I just I downgraded qt5-base plasma-desktop and plasma-workspace using "downgrade" from AUR to those in my cache (qt 5.15.12 and plasma 5.23.5). Just those three... and sleep worked fine again.
Comment 1 samvo 2022-02-16 23:06:10 UTC 
Same problem on startup: black screen with movable pointer.
Cant get debug info
KDE neon 5.24.1 + Wayland + Mesa 22 (radeon)
Comment 2 Jürgen Richtsfeld 2022-02-20 17:09:32 UTC 
Same here on Arch Linux, system info:

Operating System: Arch Linux
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.10-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8705G CPU @ 3.10GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

after returning from blank screen or hibernation, I only see a blank window and cannot unlock my session (this also doesn't work when unlocking the session from a text console).

dmesg shows:

kwin_wayland[975]: segfault at 0 ip 00007f91431a6144 sp 00007ffe7b80d690 error 4 in libxcb.so.1.1.0[7f91431a5000+13000]
Code: bc 01 00 48 39 dd 75 ee 5b 5d 41 5c c3 66 0f 1f 84 00 00 00 00 00 41 57 49 89 d7 44 89 c2 41 56 41 55 41 54 55 53 48 83 ec 38 <44> 8b 07 64 48 8b 04 25 28 00 00 00 48 89 44 24 28 31 c0 45 85 c0
Comment 3 Jürgen Richtsfeld 2022-02-22 22:16:14 UTC 
Created attachment 147060 [details]
stacktrace from systemd-coredump

After this just happened again I found a hopefully related and helpful stacktrace in my journal.

This was on an ArchLinux with all packages up to date (except the kernel):

Operating System: Arch Linux
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.15.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8705G CPU @ 3.10GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630
Comment 4 m1st0 2022-03-30 10:20:16 UTC 
I developed this issue after installing Kernel 17.1, but can't nail down what changed.  I also tried to fix it by obtaining a current linux-firmware package 20220314.gitcd01f857-0ubuntu2 .  I could not return to when I didn't have this issue on booting older kernels either.  That may be unnecessary info, but below is what I do see.

My kwin_wayland goes to 100%, but no keyboard or mouse input is available.  If I remotely login, I can kill kwin_wayland and regain mouse movement and keyboard input but have to restart things of course. I also tried to restart SDDM another time by remote login using systemctl, but I didn't get much further than a black screen after login.

Operating System: Kubuntu 21.10
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.2
Kernel Version: 5.17.1-051701-generic (64-bit)
Graphics Platform: Wayland
Active Graphics Processor: Mesa Intel® HD Graphics 530
Comment 5 m1st0 2022-04-07 01:20:02 UTC 
Created attachment 148010 [details]
attachment-9790-0.html

** Removed at the request of the author **
Comment 6 m1st0 2022-04-07 01:38:26 UTC 
Any helpful relationship?

Xwayland crash in gdm as screen off and touchscreen detach.
https://bugs.launchpad.net/oem-priority/+bug/1948894
Comment 7 Ben Cooksley 2022-04-07 18:13:55 UTC 
The content of attachment 148010 [details] has been deleted
Comment 8 Vlad Zahorodnii 2023-06-01 11:58:11 UTC 
Can you confirm whether the issue is present in KDE Plasma 5.27?
Comment 9 Bug Janitor Service 2023-06-16 03:45:16 UTC 
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!
Comment 10 mesinodd 2023-06-17 15:41:24 UTC 
wasnt a bug from plasma