Nvidia, Proprietary Linux driver: Xlibre-25.1.2 and Mesa-26.0.4 don't play along

Graphics / Linux Linux
1

Describe your issue

I have been using Xlibre-25.1.2 for over two months.
I have an NVIDIA GeForce RTX 4060/PCIe/SSE2. I use the proprietary drivers. I am on Gentoo Linux, Kernel version 6.18.18.
Today, I updated from Mesa 26.0.3 to 26.0.4..

This resulted in a variety of issues, such as.

[25259.051512] vkcube[515018]: segfault at 180 ip 00007fbc21e49f33 sp 00007fffc3683518 error 4 in libnvidia-glcore.so.590.48.01[d3ff33,7fbc2137a000+1e2a000] likely on CPU 3 (core 3, socket 0)

I know for a fact that the Nvidia driver itself wasn’t updated since 15 days prior (590.48.01-r1). /var/log/Xorg.0.log would start ballooning to up to 7 gigabytes large, full of logs that said "_XSERVTransSocketUNIXAccept: accept() failed ".

Updatring the Nvidia drivers to 595.58.03 and rebooting temporarily fixed it, but eventually, the problem started to resurface. Logging out and back in solved the issue, but resulted in SDDM consuming 6 gigabytes of RAM (wtf, it normally only consumes 2.2 megabytes for me).

Eventually, I downgraded Mesa to 25.3.6, rebooted, and now everything is working fine just fine. /var/log/Xorg.0.log is just 41.3 kilobytes large, not 7 gigabytes. SDDM consumes only 2.2 megabytes of RAM, Applications like vulkaninfo, vkcube, glxinfo, glxgears and gwenview open up correctly (previously, the command line would hang when I would try to invoke them, they would not start).

I’m not raising this issue to ask for a fix, because the problem is most likely a regression in Mesa - not something for Nvidia’s developers to fix. I’m only putting this here as a warning to NOT update to Mesa 26.0.4 if you have my specific setup.

Steps to reproduce

  1. Have Xlibre-25.1.2, Mesa-26.0.4 and Nvidia’s proprietary drivers (either 590.48.01-r1 or 595.58.03) installed on your Linux system.

  2. Run the system.

  3. Eventually, you will run out of the ability to start new X applications.

What did you expect?

Normal operation.

Additional Information

I’m not raising this issue to ask for a fix, because the problem is most likely a regression in Mesa - not something for Nvidia’s developers to fix. I’m only putting this here as a warning to NOT update to Mesa 26.0.4 if you have my specific setup.

I have raiseed his issue for Mesa too. As well as Xlibre.

2

completely out of curiosity: apart from this issue just mentioned with Mesa-26, how is your general experience with Xlibre + NV, if you would be so kind?
Thanks :)

3

It’s pretty good. No complaints at all. It works right out of the box.

4

I have upgraded to Xlibre-25.1.5, MESA-26.0.7 and Nvidia-595.71.05 from Xlibre-25.1.2, Mesa-26.0.4 and Nvidia-595.58.03 (though this update came earlier than the other two, days earlier). I used the system for an entire day without a reboot and it worked just fine. So far, I have been using the system 3 hours since the last bootup, and so far, no issues.

Not sure if updating from 25.1.2 to 25.1.5 fixed it, or if the MESA update from 26.0.4 to 26.0.7 fixed it.