-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mesa drivers problem and GLIBC version not found (wrong version) #263940
Comments
Yes, unfortunately mesa is prone to issues when you mix versions, i.e. running packages from (very) different versions of nixpkgs that the NixOS version. |
This reverts commit a9a28ff. NixOS/nixpkgs#263940
I'm running into a similar issue:
I'm using the exact same system flake (there are minor differences, where a couple modules are present on one, but not the other) on another pc and vulkan works there. The overall system flake is also the same. Literally the same commit
(I at the moment don't actually know how I update the channel to 23.11. I need to look into that.) Edit: I found the difference of the channel to actually be the issue. |
For reference, a single nixpkgs commit only has a single glibc (version). And stable releases never do major glibc upgrades (like |
duplicate of #216361 |
Describe the bug
Running some software that uses gpu drivers (mesa) throws and issue
version `GLIBC_2.38' not found
.Mesa version is 23.1.9 (current unstable)
ldd --version output is
ldd (GNU libc) 2.38
It appears by error messages that nix is using the older glibc, 2.37 (current stable)
There were previous issues like this and only fix they had is to unset
LD_LIBRARY_PATH
from env,however running
env | grep LD
doesn't output anything.part of the output when running vulkaninfo --summary:
In my configuration.nix file i have the following set:
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
No glibc errors, shows output of vulkaninfo
Screenshots
Notify maintainers
@vcunat
Metadata
The text was updated successfully, but these errors were encountered: