555 release feedback & discussion

[jensgw]

Kernel 6.1.0-0.deb11.18
NVIDIA 555.42.02

Alt+Tab in fullscreen crashes vulkan playing star citizen - might also happen in windowed mode.
Also happens with the 550 drivers.

[asubstanced]

This release fixed an issue enabling HDR via KDE on a Samsung QN90B Tv. Before it would not enable at all. Still though the display is super saturated as I guess the colour space is not being correctly negotiated.

[whelanh]

Thank you very much simulacrum72 for your post. I tried turning off G-Sync using the controls on my LG ULTRAWIDE (440x1440 px - 34.15 inches, 109.21 ppi) monitor. Unfortunately for me that did not bring up a signal when SDDM login screen should have appeared. It has convinced me though that this is an issue between the 555 driver and my monitor (since I am running exactly the same CachyOS-Arch derivative setup on my laptop and there are no problems with the 555 driver there). Perhaps there is another monitor setting change that would help, but not sure what it would be at this point.

[ManniX-ITA]

I have an RTX 3090 running headless on my NAS server with debian 11 with 5.11.22-7-pve kernel.
Installed the drivers via apt, legacy mode, as cuda-drivers.

Today I triggered the update from 550 to 555.

What a disaster, a massive disaster…

First, apparently without any reason, the open drivers have been installed.
Big mess to uninstall and reinstall everything properly.

Second, the drivers doesn’t work properly.
Calling nvidia-smi would take often dozens of seconds and sometimes failing with a kernel message complaining about a CPU core unresponsive, taxed by nvidia-smi.
The most shocking discovery was that the 3090 went from 10W in idle to 122W.

I tried to return back to 550 installing cuda-drivers-550 and it didn’t work.
Maybe I missed something but it ended up installing still the 555.

I had to go back to the runfile and will probably stay with it for a long time if not forever.
Got the same result installing 555 via the runfile, doesn’t work and idles at 122W.
installed 550 via the runfile and everything is finally back to normal.

[kodatarule]

It hasn’t been resolved for me, kwin still spams that it cannot work, maybe gamescope session directly works, but for KDE still nope.

[asubstanced]

@kodatarule

maybe gamescope session directly

I ‘think’ still get some log spamming that things are not working, which I suspect is the colour space issue… but I need to remind myself of the original error and if journalctl is where I saw the error so that I can look at it again properly.

Are you doing it through display port or HDMI? I am currently on a DP → HDMI 2.1 converter. I am due to upgrade to a RTX 3080 so then can test native HDMI 2.1 connection and see if it makes a difference.

[kodatarule]

Direct HDMI connection.

[BlueGoliath]

Can anyone at Nvidia explain how these process memory usage numbers add up to the total? And why is XWayland taking up 820 MB?

And why does nvmlDeviceGetSamples bug out whenever the GPU is under load?

[shelter]

All i know is that depending on where you look, the total GPU memory usage is different.
nvidia-smi reports one thing, when tools like nvtop/mangohud shows other numbers.

[UrbenLegend]

Got a hard hang today when attempting to suspend. Seems like there’s a crash in the open kernel module. Here are the truncated logs:
suspend_hang.txt (124.9 KB)

System Info:
Operating System: Arch Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 w/ 555.42.02 drivers + open kernel module
Product Name: X570 Taichi

[pintore270]

Same issue when suspending Nobara on latest 555, don’t know if correlated. Tell me what logs to output if needed. Eather way I have to manually reboot my pc after suspension, otherwise it’s hard stuck on something.

[damnkrat]

Getting this in journald with 555 drivers. Plasma do not show up at all on wayland - black screen. X11 is fine

мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: OpenGL vendor string:                   NVIDIA Corporation
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: OpenGL renderer string:                 NVIDIA GeForce RTX 3060/PCIe/SSE2
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: OpenGL version string:                  3.1.0 NVIDIA 555.42.02
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: Driver:                                 NVIDIA
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: Driver version:                         555.42.2
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: GPU class:                              Unknown
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: OpenGL version:                         3.1
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: GLSL version:                           1.40
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: Requires strict binding:                no
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: Virtual Machine:                        no
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: Timer query support:                    yes
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:52:44 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible

мая 29 17:53:12 dannkuntPC kwin_wayland[1707]: kwin_wayland_drm: Checking test buffer failed!
мая 29 17:53:12 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:53:12 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:53:12 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:53:12 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:53:12 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:53:12 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
мая 29 17:53:12 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
мая 29 17:53:12 dannkuntPC kwin_wayland[1707]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"

Here is my smi

❯ nvidia-smi
Wed May 29 18:18:09 2024       
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 555.42.02              Driver Version: 555.42.02      CUDA Version: 12.5     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3060        On  |   00000000:09:00.0  On |                  N/A |
| 52%   45C    P5             30W /  170W |    2489MiB /  12288MiB |     33%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                         
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      1193      G   /usr/lib/Xorg                                 520MiB |
|    0   N/A  N/A      1739      G   /usr/bin/kwin_x11                             107MiB |
|    0   N/A  N/A      1808      G   /usr/lib/kactivitymanagerd                      2MiB |
|    0   N/A  N/A      1813      G   ...b/polkit-kde-authentication-agent-1          3MiB |
|    0   N/A  N/A      1814      G   /usr/lib/org_kde_powerdevil                    52MiB |
|    0   N/A  N/A      2206      G   /home/dannkunt/64gram/Telegram                  2MiB |
|    0   N/A  N/A      2299      G   /usr/bin/konsole                                2MiB |
|    0   N/A  N/A      2304      G   /usr/lib/firefox/firefox                      255MiB |
|    0   N/A  N/A      2305      G   /usr/bin/dolphin                                2MiB |
|    0   N/A  N/A      2308      G   /usr/bin/dolphin                                2MiB |
|    0   N/A  N/A      2317      G   /usr/bin/kate                                   2MiB |
|    0   N/A  N/A      3645      G   ...bin/plasma-browser-integration-host          2MiB |
|    0   N/A  N/A      4568      G   /usr/bin/krunner                                8MiB |
|    0   N/A  N/A      4625      G   /usr/bin/plasmashell                         1410MiB |
+-----------------------------------------------------------------------------------------+

[BlueGoliath]

That’s because they either use V1 or V2 memory usage functions. That’s not what’s going on here. Nvidia own tools are reporting wrong memory usages:

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 555.42.02              Driver Version: 555.42.02      CUDA Version: 12.5     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 4060        Off |   00000000:0C:00.0  On |                  N/A |
|  0%   42C    P8             N/A /  115W |    1726MiB /   8188MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                         
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      1450      G   /usr/bin/gnome-shell                          159MiB |
|    0   N/A  N/A      1901      G   /usr/lib/xdg-desktop-portal-gnome               2MiB |
|    0   N/A  N/A      2033      G   /usr/bin/Xwayland                             820MiB |
|    0   N/A  N/A      2165      G   ...08,262144 --variations-seed-version        178MiB |
|    0   N/A  N/A      2418      G   ...73,262144 --variations-seed-version         74MiB |
|    0   N/A  N/A      2569      G   /usr/bin/nautilus                              42MiB |
|    0   N/A  N/A      3047      G   ...local/share/Steam/ubuntu12_32/steam          2MiB |
|    0   N/A  N/A      3555      G   ./steamwebhelper                               34MiB |
|    0   N/A  N/A    100678      G   /usr/bin/gnome-calculator                      19MiB |
|    0   N/A  N/A    168990      G   /usr/bin/gnome-system-monitor                  45MiB |
|    0   N/A  N/A    664184      G   /usr/lib/jvm/default/bin/java                  62MiB |
+-----------------------------------------------------------------------------------------+

What does XWayland even need 820 MB for? The GPU only has 8GB of VRAM and almost 1/4 is being used at the desktop.

[adrian.nievergelt]

For me DotA2 also segfaults on the loading screen. Kwin wayland 6.0.90.1 runs fine otherwise.

[shelter]

Yeah, I notice my Xwayland memory usage has gone up too. Yesterday it was using 88MB, now it’s at 250MB. Even if I close some X11 apps, Xwayland GPU memory usage doesn’t go down.
But I don’t think this is the right place to ask, it might be an Xwayland memory leak?

[kodatarule]

Just wanted to make small update here, first in regards to the stuttering it seems to be problem with triple buffering and there was a merged MR to fix that, you can find additional information here: backends/drm: allow having two frames in flight ("triple buffering") (!4833) · Merge requests · Plasma / KWin · GitLab

As for the hangs/freezes, it turns out it wasn’t a freeze, but instead it just hangs the plasma panel/widgets/desktop/etc when you hide the panel, as long as you don’t hide panel or make it to dodge windows it’s fine, I have filed a bug report in regards to that here: 487728 – Plasma panel/widgets freeze randomly with explicit sync, can be unfreezed by going into overview

EDIT: Forgot to mention(though I’ve described it in the bug report) one way to workaround that issue with hidden panel causing freeze is to trigger the overview (super+w) and to close it again, that is as long as the panel is visible and not hidden.

[PacketAuditor]

555 has been mostly good to me besides some stability issues. Who knows if it’s the beta video driver or beta KDE 6.1.

Looking forward to 560, hopefully we get VRR with multiple displays enabled.

[azureskywarden]

I’m getting severe graphical glitch on Debian 12 Gnome. It usually happens 20-30 minutes after booting. Opening many apps seem to help trigger it, though I’m not exactly using “heavy” ones. Just Chrome, Discord and a built-in Text Editor. Here’s my SMI. Any help would be very appreciated because this is really hindering my work.

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 555.42.02              Driver Version: 555.42.02      CUDA Version: 12.5     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 4070 ...    On  |   00000000:01:00.0 Off |                  N/A |
| N/A   43C    P3             11W /   55W |      15MiB /   8188MiB |      6%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                         
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      1841      G   /usr/lib/xorg/Xorg                              4MiB |
+-----------------------------------------------------------------------------------------+

[jsalatas]

I’m still having the following issue that I previously reported

BUG: wayland EGL applications not working with dual nvidia gpus

I have a Dell Precision 5820 workstation with dual GPUs (RTX A2000 and RTX A5000) and wayland egl apps don’t work. They just display garbage. The issue is always reproducible in my system under both kde plasma 6 and weston compositor. Easiest way to reproduce it is to start weston compositor and then run the weston-simple-egl application. I have tried the 535, 545 and 550 drivers. You can see some screenshots of the issue in the bug report I created for kde plasma at https://bugs.kde.org/show…

[shelter]

There got to be some GPU memory leak somewhere, because now my Xwayland process is taking up 400MiB…
Seems like opening and closing X11 apps makes it grow and it never frees the memory.
@aplattner This one is pretty bad. If it’s the driver or Xwayland itself, I can not tell.

Xwayland on a freshly booted system:
/usr/bin/Xwayland 9MiB

Xwayland after 3 days (with all X11 apps closed):
/usr/bin/Xwayland 409MiB