I’m experiencing these crashes with driver 575.64 on a 5080 and KDE Plasma 6.4.1.
Guessing there’s no resolution in sight? This has dragged on a while…
It’s pretty easy to work around:
systemctl --user restart plasma-plasmashell
And as amrits just posted they have an internal issue and are able to reproduce it, which means a fix should be in the pipeline. If there was no resolution in sight then it would be one of the threads with no Nvidia posts.
Does anyone know if there was any last passing driver.
Best I can give you is that it’s been happening since January, so it would have been a driver prior to this year.
This issue is still occuring on my end as well, almost daily. every instance of plasmashell crashing is due to this issue.
$ coredumpctl --reverse
Hint: You are currently not seeing messages from other users and the system.
Users in groups ‘adm’, ‘systemd-journal’, ‘wheel’ can see all messages.
Pass -q to turn off this notice.
TIME PID UID GID SIG COREFILE EXE SIZE
Wed 2025-10-01 12:09:25 PDT 802358 1000 984 SIGTRAP present /usr/bin/plasmashell 87M
Mon 2025-09-29 20:03:24 PDT 624386 1000 984 SIGTRAP present /usr/bin/plasmashell 105.3M
Sat 2025-09-27 13:37:57 PDT 562309 1000 984 SIGSEGV present /home/jackw/.local/share/Steam/steamapps/common/Proton Hotfix/files/bin/wine64-preloader 267.5M
Fri 2025-09-26 22:37:25 PDT 496436 1000 984 SIGTRAP present /usr/bin/plasmashell 121M
Thu 2025-09-25 17:55:24 PDT 465859 1000 984 SIGTRAP present /usr/bin/plasmashell 77.1M
Thu 2025-09-25 11:42:02 PDT 416682 1000 984 SIGTRAP present /usr/bin/plasmashell 100.2M
Wed 2025-09-24 13:40:35 PDT 262467 1000 984 SIGSEGV present /usr/bin/plasmashell 79.7M
Wed 2025-09-24 12:03:18 PDT 280779 1000 984 SIGSEGV present /usr/bin/ark 4.5M
Wed 2025-09-24 09:37:26 PDT 187396 1000 984 SIGTRAP present /usr/bin/plasmashell 110M
Mon 2025-09-22 16:47:27 PDT 62146 1000 984 SIGTRAP present /usr/bin/plasmashell 105M
Additionally, one of the fastest ways I’ve generated entries in sync_file is by just hovering over my taskbar icons. Every time a popup occurs, they end up looking glitchy, broken and awful on occasion, as if they’re not the right size. then, after doing that for a bit, running
lsof -p $(pidof plasmashell)|grep sync_file|count
ends up skyrocketing. I was able to get it from 100 to 376 within about a minute.
When the amount of entries gets to around 850 or so, thumbnails stop loading entirely and the taskbar/files on my desktop stop responding completely.
I’ve uploaded a video demonstrating most of these behaviors. In this video, I cause KDE in Arch to crash in less than 3 minutes simply by rubbing my taskbar:
Can confirm that issue still reproducible on KDE 6.4.5 Wayland.
Nvidia driver: 580.95.05 ( “open” driver ).
1 Like
I reproduced this problem and filed internal bug 5556719 to track down where the leak is happening.
2 Likes
Would it be possible for you guys to try egl-wayland2? We’re working on replacing the original egl-wayland codebase with that one and it resolved the problem for me.
Installed egl-wayland2 and rebooted. Doesn’t seem to have fixed it for me.
❯ lsof -p $(pidof plasmashell)|grep sync_file|count
119
❯ notify-send test
❯ lsof -p $(pidof plasmashell)|grep sync_file|count
123
❯ notify-send test
❯ lsof -p $(pidof plasmashell)|grep sync_file|count
127
Maybe I installed it wrong?
❯ meson setup build
The Meson build system
Version: 1.9.1
Source dir: /home/arimil/Development/egl-wayland2
Build dir: /home/arimil/Development/egl-wayland2/build
Build type: native build
Project name: nvidia-egl-wayland2
Project version: 1.0.0
C compiler for the host machine: cc (gcc 15.2.1 "cc (GCC) 15.2.1 20250813")
C linker for the host machine: cc ld.bfd 2.45.0
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: YES (/usr/bin/pkg-config) 2.5.1
Run-time dependency libdrm found: YES 2.4.126
Run-time dependency threads found: YES
Run-time dependency eglexternalplatform found: YES 1.2
Run-time dependency egl found: YES 1.5
Checking if "typeof" compiles: YES
Run-time dependency gbm found: YES 25.2.4-cachyos1.2
Run-time dependency wayland-client found: YES 1.24.0
Library dl found: YES
Run-time dependency wayland-egl-backend found: YES 3
Run-time dependency wayland-protocols found: YES 1.45
Build-time dependency wayland-scanner found: YES 1.24.0
Program /usr/bin/wayland-scanner found: YES (/usr/bin/wayland-scanner)
Build targets in project: 2
Found ninja-1.12.1 at /usr/bin/ninja
❯ ninja -C build
ninja: Entering directory `build'
[32/32] Linking target src/wayland/libnvidia-egl-wayland2.so.1.0.0
❯ sudo ninja -C build install
ninja: Entering directory `build'
[0/1] Installing files
Installing src/wayland/libnvidia-egl-wayland2.so.1.0.0 to /usr/local/lib
Installing /home/arimil/Development/egl-wayland2/src/wayland/09_nvidia_wayland2.json to /usr/local/share/egl/egl_external_platform.d
Installing symlink pointing to libnvidia-egl-wayland2.so.1.0.0 to /usr/local/lib/libnvidia-egl-wayland2.so.1
Installing symlink pointing to libnvidia-egl-wayland2.so.1 to /usr/local/lib/libnvidia-egl-wayland2.so
I can confirm that the issue still occurs on egl-wayland2. I can clearly notice a difference in performance, however, as I can actually cause the crashes to occur much faster now that these modals load instantly instead of taking a bit of time.
I can make it crash in 2 minutes instead of 3 now. Handles continue to accumulate even though they should be freed.
1 Like
I am also experiencing this or a similar issue (on Bazzite 42), noting the sync_file count jumping every time I click on and off a KDE stacked application icon.
I also see semi-frequent KDE crashes with “Too many open files” in the log.
This is with Plasma 6.4.5, Qt 6.9.2, nVidia driver 580.95.05.
I confirmed the file descriptor leak still occurs with Plasma 6.5.1, Qt 6.10.0 in Bazzite 43. This version still includes nVidia driver 580.95.05. I will test again as future version(s) become available.
edit The leaked handles appear to correspond to sync_file descriptors.
edit2 For now, a workaround is to run “plasmashell --replace &” once the file descriptor count gets dangerously high, e.g. 600+. This results in almost all the descriptors getting dropped.
Just updating from the main thread, vrachatte confirmed that internal Nvidia ticket 5556719 is still being worked for this issue.
@vrachatte this week, I discovered that using kcmshell6 qtquicksettings and changing Plasma to software rendering completely avoids the sync_file leaks. The lsof command now only shows 1 sync_file handle open at any given time, instead of hundreds.
For me, software rendering in Plasma works fine, though I still hope the leak case using Nvidia hardware rendering is fixed eventually.
For even more fun, you can try the Vulkan renderer and restart plasmashell. Then you’ll have 0 sync_file handles open.
1 Like
KDE devs do not recommend doing this, by the way.
Meanwhile I am on 590.44.01, and sync_file handles are not increasing with time. I opened a notification with notify-send, and it added one handle, until the notification closed, at which point the handle was closed.
It sounds like the bug was actually fixed in 590.44.01 then? I didn’t see it in the patch notes.
I hesitate to upgrade given the other regressions discussed in the 590 thread.
Tested 580.119.02 and the Beta 590.44.01. Sadly the issue still appears in those versions.
In “normal” usage I get this issue, when copying files from a network share all day, which causes the plasma notification for the copying process to appear. It froze the entire desktop environment, thankfully the copying process was still running in the background.
Here a test using the script from the thread:
HOWEVER after installing egl-wayland2 (1.0.0.rc.r51.gada1c37 from Arch Repos) + using 590.44.01 and rebooting, the issue went away! The open descriptors stay consistent:
So it’s kinda fixed, however I am unsure when egl-wayland2will replace the original egl-wayland package. If I may ask about the roadmap for that? And if it’s “““save””” to use for every day use? @aplattner
I should note that using 580.119.02with egl-wayland2doesn’t fix the issue, so the 590 version seems to be required..
This is anecdotal, but negativo17 manages a Linux Nvidia driver repository that is used for Bazzite (and other distributions?). When I was asking about something, they mentioned egl-wayland2 is not yet ready.
So I would assume it is still not safe for broad use.