I have this problem with fullscreened Shatterline launched via Proton, and fullscreen Minecraft both launched on NVIDIA GPU (offload) with AMD APU as the main card. Present only on Wayland.
So if I launch some applications with my NVIDIA GPU in fullscreen mode on an external HDMI display connected to my laptop, external HDMI output will freeze, but the application will not crash and even will keep rendering on NVIDIA GPU. If I try to replug the frozen display or just disable-enable it via KDE Plasma settings, my whole graphics system will freeze, and after that I’m not even able to switch to a different TTY.
Problem started to appear after a relatively recent NVIDIA driver update.
A bit more details about my previous attempts to retest this bug.
Retest was done at the same laptop, the same OS version (snapshot) and even with the same KDE Plasma and Kwin versions. The only thing that I changed in my system is the official NVIDIA driver version (installed G05 instead of G06 [see the official NVIDIA driver repo for openSUSE Tumbleweed]).
Also this bug appeared during 5xx driver updates, but not during upgrade from 4xx to 5xx.
Here what my zypper will do if I ask him to downgrade to the G05:
root@yspace ~# LANG=C zypper install nvidia-computeG05
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: the installed nvidia-computeG06-525.78.01-16.1.x86_64 conflicts with 'nvidia-computeG05' provided by the to be installed nvidia-computeG05-470.161.03-58.2.x86_64
Solution 1: Following actions will be done:
deinstallation of nvidia-computeG06-525.78.01-16.1.x86_64
deinstallation of nvidia-computeG06-32bit-525.78.01-16.1.x86_64
deinstallation of x11-video-nvidiaG06-525.78.01-16.1.x86_64
deinstallation of x11-video-nvidiaG06-32bit-525.78.01-16.1.x86_64
deinstallation of cuda-runtime-12-0-12.0.0-1.x86_64
deinstallation of cuda-runtime-11-8-11.8.0-1.x86_64
deinstallation of cuda-12-0-12.0.0-1.x86_64
deinstallation of cuda-11-8-11.8.0-1.x86_64
downgrade of cuda-12.0.0-1.x86_64 to cuda-11.4.4-1.x86_64
deinstallation of nvidia-gfxG06-kmp-default-525.78.01_k6.1.3_1-16.1.x86_64
deinstallation of nvidia-glG06-525.78.01-16.1.x86_64
deinstallation of nvidia-glG06-32bit-525.78.01-16.1.x86_64
Solution 2: do not install nvidia-computeG05-470.161.03-58.2.x86_64
Choose from above solutions by number or cancel [1/2/c/d/?] (c): 1
Resolving dependencies...
Resolving package dependencies...
The following package is going to be downgraded:
cuda
The following 5 recommended packages were automatically selected:
nvidia-computeG05-32bit nvidia-glG05 nvidia-glG05-32bit x11-video-nvidiaG05 x11-video-nvidiaG05-32bit
The following 7 NEW packages are going to be installed:
nvidia-computeG05 nvidia-computeG05-32bit nvidia-gfxG05-kmp-default nvidia-glG05 nvidia-glG05-32bit x11-video-nvidiaG05 x11-video-nvidiaG05-32bit
The following 11 packages are going to be REMOVED:
cuda-11-8 cuda-12-0 cuda-runtime-11-8 cuda-runtime-12-0 nvidia-computeG06 nvidia-computeG06-32bit nvidia-gfxG06-kmp-default nvidia-glG06 nvidia-glG06-32bit x11-video-nvidiaG06 x11-video-nvidiaG06-32bit
1 package to downgrade, 7 new, 11 to remove.
Overall download size: 272.5 MiB. Already cached: 0 B. After the operation, 416.8 MiB will be freed.
Continue? [y/n/v/...? shows all options] (y):
Just got this bug on X11.
On X11 I’m able to control the lagged external display colors via NVIDIA Xserver Settings, and just torn off-on the display in system settings in order to “fix the display”.
Also there was a system lag after turning my external display off.
Wayland? A pinned post says not everything works on wayland EGL (egl is made for apps that want and older more stable GL, not for new features).
I don’t think nVidia owes Ubuntu KDE Suse more packges (infact i wish they’d help wider platforming not favor 2 or 3, personally). You didn’t say what OS your using what version, what version of Xorg (X11 is incorrect).
“wayland” is an “X wrapper” as is gtk or kde. it is continually changing versionally - and i wouldn’t be API are stable (ie, already released features canceled in new API - which KDE and GTK continually due against all rules).
to make matteres worse, Xorg has rapidly been hacking wayland features “that can’t be removed” from X as well as GL features that cann’t be removed
this makes predicting “what one means by saying on wayland” wildly un-predictable as to determining a cause.
The problem is that no errors are logged apart from sometimes an Xid 56, “Display Engine error”, telling only what you already know, the nvidia gpu has an issue with its hdmi port.
Likely won’t help, but did you already check for a bios update?
2022-11-28 version 525.60.11
* Improved the performance of PRIME render-offloaded applications.
but wasn’t fixed with
======== Release 530 Entries ========
* Fixed a bug that prevented PRIME render offload from working for
Wayland applications when running on a system with an AMD iGPU.
Though that likely addressed a different bug.
At least the other person found a workaround by using gamescope.
Wayland is a new display server protocol that is still undergoing development and may not be fully compatible with all applications. You could try disabling Wayland and using the more established X11 display server instead same as like you can see on this page. To do this, you can log out of your current session and select the X11 session from the login screen.
X11 has the same problem, but just in a bit more delayed manner.
And your link leads to a “Best 9 Fillet Knife for Fish 2023 – Review & Buying Guide” page.