SUMMARY STEPS TO REPRODUCE 1. Play a video in fullscreen mode on YouTube (Browser:Zen) 2. Move the cursor out of the screen. 3. Move the browser back to the fullscreen video. OBSERVED RESULT System freezes for a few seconds. The video stays frozen even after system responsiveness returns. The second screen becomes unusable. EXPECTED RESULT The video should continue playing smoothly. The second screen should remain usable. The cursor movement should not cause any freezes. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.6-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82MS System Version: Yoga Slim 7 Pro 14ACH5 ADDITIONAL INFORMATION
Can you check kwin's logs when the freeze occurs? journalctl --boot --user-unit plasma-kwin_wayland > ~/log.txt Also, is there any chance that you could retrieve kwin's backtrace when the freeze occurs? You would need to ssh from another computer and attach a debugger to kwin process, e.g. sudo gdb -p $(pidof kwin_wayland) then type bt and paste the output here
Hi, Thank you for your response! I will follow the steps you’ve outlined and collect the logs and backtrace soon. I’ll update the bug report once I have the requested information. Thanks for your help!
Here's the output: Mar 28 15:56:00 fedora kscreenlocker_greet[282901]: pam_unix(kde:auth): authentication failure; logname=rvalayodapillai uid=1000 euid=1000 tty= ruser= rhost= user=rvalayodapillai Mar 28 15:56:39 fedora kwin_wayland[73620]: qt.svg: link #g917 is undefined! Mar 28 15:56:39 fedora kwin_wayland[73620]: qt.svg: link #g949 is undefined! Mar 28 15:56:39 fedora kwin_wayland[73620]: qt.svg: link #g969 is undefined!
Thanks for the information. I'll let the kwin developers take it from here.
Please attach the full kwin log here after reproducing the issue.
I found that the issue occurs only when using Firefox or its forks. It doesn't happen on Chromium-based browsers. The issue appears to be related to AMD GPUs and was resolved by setting the kernel parameter amdgpu.runpm=0.
Thanks for letting us know, and I'm glad you got this working well on your system. Since this was an issue with the AMD driver and the kernel, I'm going to close this out for now.