Bug 505967

Summary:	Plasma-wayland 6.4.0: desktop effects cause freezes, subsequence session restarts and ultimately display glitches-crashes.
Product:	[Plasma] kwin	Reporter:	apricorum <fabio9000dg>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	dec05eba, kdedev, nate
Priority:	NOR
Version First Reported In:	6.4.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description apricorum 2025-06-22 12:41:36 UTC

SUMMARY
During a gamescope session I've noticed that Alt+Tab-ing would cause a noticeable and long-lasting freeze. I did figure out it was due to gpu-screen-recorder-ui interfering, though, before I could disable it, I firstly got a notification from KDE saying "Desktop-effects restarting" (I can't remember the extact body of the notification), and, once pressed SUPER for opening the Menu Bar the system froze and lead to an glitchy output.  

STEPS TO REPRODUCE
1. Open a game using gamescope and with the following parameters under proton Hotfix: PROTON_ENABLE_WAYLAND=1 gamescope -h 1440 -f --adaptive-sync --hdr-enabled -r 165 --backend wayland --force-grab-cursor --.
2.  While in game open the gpu-screen-recorder-ui through ALT-Z.
3.  Alt-Tab

SOFTWARE/OS VERSIONS
Operating System: CachyOS Linux 
KDE Plasma Version: 6.4.0
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.3-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 9600X 6-Core Processor
Memory: 32 GiB of RAM (30.4 GiB usable)
Graphics Processor 1: AMD Radeon RX Vega
Graphics Processor 2: AMD Radeon Graphics
Manufacturer: ASRock
Product Name: B650 Pro RS

If this happens again I will take a picture and post it here. Thanks for your patience.

Comment 1 dec05eba 2025-06-22 16:30:07 UTC

This likely an amd driver bug. If you see it happen again run
sudo dmesg
to see if there is an issue reported by amdgpu. This types of issues are common for some amd users.

Comment 2 dec05eba 2025-06-22 16:32:51 UTC

What happens is that the amd driver freeze, crashes and then restarts. If you run into it again and see an issue in dmesg then report it to amd in either the mesa or drm freedesktop gitlab repositories.

Comment 3 TraceyC 2025-06-26 00:10:21 UTC

As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

Thanks.

Comment 4 Bug Janitor Service 2025-07-11 03:47:40 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2025-07-26 03:46:42 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.