SUMMARY I have a laptop and two monitors externally connected: one via USB-C to DP and the other HDMI to HDMI. The first monitor I tend to switch the input source on my first monitor so that it switches over to my Xbox and that is fine with no issues as far as my system is concerned. Sometimes though, when I switch the input source back to my Linux system, the primary monitor (the laptop) ends up freezing. This doesn't always happen, and usually when I switch the input source I can interact with my primary monitor just fine. When it's not fine, the primary monitor is frozen. That means: the cursor is frozen in state, and I can't interact with it at all. Oddly enough, the other two externally connected monitors are just fine, and I can use the cursor on those monitors; effectively there's two cursors at this point: one is frozen in state on the primary monitor, and the other I can move. Disconnecting the hdmi/usb-c cables does not work, so I effectively have to do a hard reboot to resolve the issue. STEPS TO REPRODUCE 1. Have a primary monitor connected to two external monitors 2. Switch input source on one of the monitors 3. Not sure if time-bound, but switching input source back to the Linux can result in primary monitor freezing OBSERVED RESULT Primary monitor freezes, cursor is frozen, can't interact with the primary monitor at all. External ones are fine. EXPECTED RESULT All monitors should not be frozen and I should be able to interact with them with no issues. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 Kernel Version: 6.15.3-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 ร AMD Ryzen 7 7840HS w/ Radeon 780M Graphics Memory: 62.0 GiB of RAM Graphics Processor 1: AMD Radeon RX 7600M XT Graphics Processor 2: AMD Radeon 780M Graphics Manufacturer: TUXEDO Product Name: TUXEDO Sirius 16 Gen1 Mesa: 25.1.4-arch1.1
*** This bug has been marked as a duplicate of bug 506441 ***
As this is on Wayland, it's somewhat likely to be different from bug 506441.
When the screen freezes, is there anything out of the ordinary in > sudo dmesg or > journalctl --user-unit plasma-kwin_wayland --boot 0 ? If you disable PSR (set amdgpu.dcdebugmask=0x10 as a kernel argument to do it), does it still happen?
Created attachment 183092 [details] Here is output of dmesg and journalctl
๐๐งน โ ๏ธ 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!
I attached the log a few weeks back but neglected to update the status of the bug report. Please kindly review the logs and get back to me on the prognosis.
Oh sorry, this kind of went under. The log is a bit of a mixed bag. There's a few > The main thread was hanging temporarily! which may be an issue in KWin, or it could be that it's failing to do atomic tests (or hanging in the kernel) when trying to find a way to keep all displays working. There's also one very badly delayed pageflip, and a bunch of seemingly legit > Pageflip timed out! This is a bug in the amdgpu kernel driver If you can still replicate this issue, please check in > sudo dmesg if you see similar messages about pageflip timeouts. If you do, then please report it at https://gitlab.freedesktop.org/drm/amd/-/issues If you don't see such messages, please follow https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues to get a drm debug log of the issue.
๐๐งน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.