New comment by redasamik on void-packages repository https://github.com/void-linux/void-packages/issues/32222#issuecomment-888167500 Comment: في ثلاثاء، 27 تموز، 2021 في 11:58 م، كتب saintgowron < ***@***.***>: > System > > - > > xuname: > Void 5.12.19_1 x86_64 AuthenticAMD uptodate rrrrmmnFFFF > - > > package: > nvidia-470.57.02_1 > > Expected behaviour > > Driver should be able to open the lib and run Vulkan games as usual. > Actual behaviour > > Since I updated from version 460.84_2, when trying to run Vulkan based > games (or ones using DXVK through steam proton), the programs don't launch > and the processes completely exit after about two seconds. > > The steam proton log revealed the following error message: > The NVIDIA driver was unable to open 'libnvidia-glvkspirv.so.470.57.02'. > This library is required at run time. > > I'm not really sure what the library is used for - Nvidia just lists it > under "Various libraries that are used internally by other driver > components", but since OpenGL games still work and Vulkan ones don't, I > assume it has something to do with Vulkan.. > Steps to reproduce the behaviour > > - Install / update the nvidia driver to the newest version through > xbps. > - Try to run a Vulkan based game (for example Middle Earth: Shadow of > Mordor), or any DirectX game, that gets its calls translated to Vulkan by > DXVK through Steam Proton (f.e. Mass Effect: Legendary Edition). > > What I have tried so far / additional information > > Everything worked fine before the update and the update was performed as a > full update i.e. sudo xbps-install -Su, so I did not just randomly update > single packages or anything like that. It finished without any warnings or > errors. > > I made sure that the library is actually in /usr/lib/ and /usr/lib32/ and > that the permissions were set correctly. I re-installed the packages > through xbps and restarted a few times for good measure, but to no effect. > > Another person on the subreddit had the exact same issue, so I don't think > that it has something to do with my system config. > > I also tried to manually install the driver, using the official version > from Nvidia's website - this one worked as expected, which leads me to > believe that it may actually be an issue with the package. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , or unsubscribe > > . > -- reda