Great to see more improvements! I think this has something to do with some graphical rendering information corruption of the apps/UI elements that were stored on the GPU memory before the suspend session. In case these glitches are currently happening only to apps that weren't closed and not at all to the rest of the UI after suspend sessions, then I can suggest you two options:
-
Remain with the Driver Version 570 (Open/Server, whichever you found success on), and make sure to either close all apps before suspending or after suspend, restart all apps (my suggestion) that were left open before the system entered the suspend session.
-
Another solution I once saw while questioning this issue on Claude AI was to refresh the GPU state after the suspend session, which might be helpful. Here's the output+commands I've asked Claude Haiku 4.5 AI to generate:
(Output Starts)
Wayland changes things significantly here, and it's good that your friend found it more stable than X11.
Wayland-Specific Considerations
On Wayland with Nvidia, the GPU state handling is different because the compositor (like Gnome Shell) manages the display differently. The good news is that Wayland is generally more resilient to GPU state issues, but suspend/resume can still cause problems.
Here's a Wayland-optimized version of the script (to create a new script file):
sudo nano /etc/systemd/system-sleep/nvidia-wayland-reset.sh
Add this content (from #!/bin/bash to esac):
#!/bin/bash
case $1 in
post)
# Wayland-specific GPU reset after resume
echo "Resetting Nvidia GPU for Wayland..."
# Reset GPU state without reloading modules (safer on Wayland)
nvidia-smi -pm 1 > /dev/null 2>&1
# Give Wayland compositor time to reinitialize
sleep 2
echo "Wayland GPU reset complete"
;;
esac
(press Ctrl+O followed by the Enter key to save/write the file and Ctrl+X to exit back to the terminal)
Make it executable:
sudo chmod +x /etc/systemd/system-sleep/nvidia-wayland-reset.sh
Why This Approach Works Better on Wayland
- Avoids full module reloads that can conflict with Wayland's GPU management
- Lets the Wayland compositor handle reinitalization rather than forcing it
- Works even after a restart (Yea i specifically asked if it did and it does cuz systemd executes it everytime after a suspend session)
One More Thing to Check
Since they're seeing remnants only when apps were open during suspend, they might also benefit from checking if there's a Wayland-specific Nvidia setting in their display settings or Gnome tweaks. Sometimes enabling "Nvidia PRIME" or checking GPU sync settings helps (This seems to be generic AI suggestions that might not even exist. If it does, let us know)
Has your friend noticed if the remnants appear in specific apps, or is it random? That might tell us if it's an app-level GPU cache issue versus a system-level one.
(Output Finished)
Disclaimer: As i mentioned before, the second solution is AI generated and hence it might contain mistakes. However, I went over the command lines and it looks good as per my knowledge. I've written my help tips in the output within round brackets () for better clarity.
(and it came true 
)
