Bug 512168

Summary: Kwin_wayland crashes after resume from sleep
Product: [Plasma] kwin Reporter: Denis Shkuratov <sunabouzu.desert>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: REPORTED ---    
Severity: crash CC: kdedev, sunabouzu.desert
Priority: NOR Keywords: wayland-only
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Log

Description Denis Shkuratov 2025-11-16 07:09:13 UTC
Created attachment 186832 [details]
Log

SUMMARY

Sometimes (mostly when I get my PC into sleep for a night) kwin_wayland crashes. I have no stable repro, but  its really annoying since I lost everything I opened before.

STEPS TO REPRODUCE
1. Put PC to sleep
2. Wait
3. Resume from sleep

OBSERVED RESULT

kwin_wayland crashes, Xwayland applications (Steam, for example) lose native scaling.

EXPECTED RESULT

kwin_wayland doesn't crash

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 32 GiB of RAM (30.9 GiB usable)
Graphics Processor: AMD Radeon RX 9070 XT

ADDITIONAL INFORMATION
I use KDE since F42 and never see anything like this before. I don't really remember when its start happening.

Some other info

Mesa:
user@fedora ~> glxinfo -B | grep Mesa
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.2.7
OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.2.7
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.2.7

I undervolted my CPU (Ryzen 7600) and I started get this more often? But I also update my KDE to latest version, so I don't see any connections to this crashes. Games are stable and prime95 doesn't generate any errors or unstable behavior.

I attached logs from crash
Comment 1 TraceyC 2025-11-18 23:16:42 UTC
Relevant part of the backtrace

Stack trace of thread 11192:
#0  0x00007fef918803cc __pthread_kill_implementation (libc.so.6 + 0x743cc)
#1  0x00007fef9182618e raise (libc.so.6 + 0x1a18e)
#2  0x00007fef95458071 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x5071)
#3  0x00007fef918262c0 __restore_rt (libc.so.6 + 0x1a2c0)
#4  0x00007fef94d8fe77 _ZN4KWin11DrmPipeline15commitPipelinesERK5QListIPS0_ENS0_10CommitModeERKS1_IPNS_9DrmObjectEE (libkwin.so.6 + 0x38fe77)
#5  0x00007fef94d7b775 _ZN4KWin6DrmGpu9doModesetEv (libkwin.so.6 + 0x37b775)
#6  0x00007fef91f6855a _Z10doActivateILb0EEvP7QObjectiPPv (libQt6Core.so.6 + 0x16855a)
#7  0x00007fef91f78bb3 _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt6Core.so.6 + 0x178bb3)
#8  0x00007fef91f599d5 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1599d5)
#9  0x00007fef9323db1f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x3db1f)
#10 0x00007fef91efcaa8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0xfcaa8)
#11 0x00007fef920d1eb8 _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x2d1eb8)
#12 0x00007fef920d61ab _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2d61ab)
#13 0x00007fef92cfe1f2 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x6fe1f2)
#14 0x00007fef91f09603 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x109603)
#15 0x00007fef91f04df9 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x104df9)
#16 0x000055bdd3ac1999 main (/usr/bin/kwin_wayland + 0xe999)
#17 0x00007fef9180f5b5 __libc_start_call_main (libc.so.6 + 0x35b5)
#18 0x00007fef9180f668 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x3668)
#19 0x000055bdd3ac7d55 _start (/usr/bin/kwin_wayland + 0x14d55)
Comment 2 Denis Shkuratov 2025-11-19 20:15:22 UTC
I get this issue almost always when I put my PC to sleep for a long time. If I can provide any kind of information for help fix this - let me know.
Comment 3 Denis Shkuratov 2025-11-23 12:15:27 UTC
I reset my BIOS completely - and have this issue anyway. So this culprit is - new 6.17 kernel from f43, new Mesa or KDE itself.
Comment 4 Denis Shkuratov 2025-11-24 19:12:37 UTC
Not an issue on kwin_x11, so I don't know. Everything works fine except kwin_wayland.