Bug 511808

Summary:	screen freezes when switching to dGPU content on wayland (AMD)
Product:	[Plasma] kwin	Reporter:	contact
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	NEEDSINFO WAITINGFORINFO
Severity:	normal	CC:	kde, nate, xaver.hugl
Priority:	NOR
Version First Reported In:	6.5.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description contact 2025-11-08 08:06:27 UTC

SUMMARY
When playing Baldours Gate 3 I've noticed that the screen would freeze as soon as the game started loading. However I also noticed that the menu sounds still seemed to work and I even managed to stream the game to my steam deck even tho the desktop was hard-locked not even recovering when I tried to Ctrl+Alt+F into a different session.

I am assuming that something crashes when dGPU content is being displayed. This also happened with another game (CONTROL) that I tested even tho in this case I was able to recover by switching to a different session and killing the process.

STEPS TO REPRODUCE
1. open a kde-wayland session
2. run a game that uses the dGPU

OBSERVED RESULT
Display Freezes

EXPECTED RESULT
Gameplay

SOFTWARE/OS VERSIONS
Operating System: NixOS 25.11
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 32 GiB of RAM (27.2 GiB usable)
Graphics Processor 1: AMD Radeon 780M Graphics
Graphics Processor 2: AMD Radeon RX 7700S
Manufacturer: Framework
Product Name: Laptop 16 (AMD Ryzen 7040 Series)
System Version: AG

ADDITIONAL INFORMATION

I am filing this bug here, because it does not happen on x11 but wayland only and the wayland issue tracker says day-to-day issues with wayland are responsibility of the implementation.

Comment 1 contact 2025-11-08 08:14:54 UTC

I've noticed how this could also be a proton bug. I will try to replicate this issue with Godot to test that hypothesis.

Comment 2 contact 2025-11-08 12:23:58 UTC

So when I run my Godot Project in exclusive fullscreen and set it to use wayland it does not produce the same issue.

So this seems to be an issue that is either exclusive to proton or exclusive to BG3 ... I think it is more likely proton because it also effects control.

I am leaving this open in the hope that maybe it is something the kde team can do something about even if it is helping me find the right angle to solve it. I will try and see if I can get this reported to ... proton I guess?

Comment 3 Zamundaaa 2025-12-15 15:51:36 UTC

>  the desktop was hard-locked not even recovering when I tried to Ctrl+Alt+F into a different session.
So, no input works at all when this happens?

Please reproduce the issue, and then attach the output of
> journalctl --user-unit plasma-kwin_wayland --boot 0
here afterwards. If you need to reboot in between, just use "--boot -1" instead, though you can also ssh into the system to avoid that (and to avoid having to forcefully shut down the PC).