From: ArmedAviator <ArmedAviator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nvidia-470.57.02_1: driver can't open "libnvidia-glvkspirv.so.470.57.02"
Date: Wed, 28 Jul 2021 04:16:42 +0200 [thread overview]
Message-ID: <20210728021642.VbEEiHE1fY9YNW6x-kjpDnG9R00gduZEhv_NtGfSQ4M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32222@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
New comment by ArmedAviator on void-packages repository
https://github.com/void-linux/void-packages/issues/32222#issuecomment-887957395
Comment:
Just throwing ideas out there....
Is there perhaps a rebuild needed against the new library version in a different package? I.e. libwine, vkd3d, etc.? As mentioned, this happened to me when Void upgraded from 455 to 460 and a few days later it suddenly worked after another system update. I don't recall what packages were updated, but I can only imagine something built against it fixed it. Doesn't make much sense, in my limited experience, since the NVIDIA driver knows where the libs are and named the file directly and correctly in the error from Steam.
Here is the full output from Steam when trying to start Doom Eternal with Proton 6.3.
https://pastebin.com/9iGtEz6V
Additionally, are you running Steam from the XBPS package or from a flatpak? I'm running it from the native package.
next prev parent reply other threads:[~2021-07-28 2:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 20:58 [ISSUE] " saintgowron
2021-07-27 22:48 ` ArmedAviator
2021-07-27 22:56 ` abenson
2021-07-27 23:22 ` abenson
2021-07-27 23:28 ` abenson
2021-07-27 23:32 ` Lolzen
2021-07-27 23:33 ` Lolzen
2021-07-27 23:34 ` abenson
2021-07-27 23:35 ` Lolzen
2021-07-27 23:43 ` ArmedAviator
2021-07-28 0:33 ` abenson
2021-07-28 0:38 ` abenson
2021-07-28 2:03 ` ArmedAviator
2021-07-28 2:09 ` abenson
2021-07-28 2:16 ` ArmedAviator [this message]
2021-07-28 2:27 ` abenson
2021-07-28 2:55 ` ArmedAviator
2021-07-28 7:03 ` Lolzen
2021-07-28 8:14 ` saintgowron
2021-07-28 8:45 ` Lolzen
2021-07-28 8:46 ` Lolzen
2021-07-28 9:39 ` abenson
2021-07-28 9:41 ` redasamik
2021-07-28 11:15 ` Lolzen
2021-07-28 14:09 ` ArmedAviator
2021-07-28 14:39 ` ArmedAviator
2021-07-28 14:45 ` ArmedAviator
2021-07-28 14:46 ` ArmedAviator
2021-07-28 18:11 ` saintgowron
2021-07-31 23:44 ` mvf
2021-08-01 7:55 ` mvf
2021-08-01 10:58 ` saintgowron
2021-08-01 11:01 ` ArmedAviator
2021-08-01 11:38 ` mvf
2021-08-01 18:29 ` RononDex
2021-08-05 12:33 ` ericonr
2021-08-05 17:08 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210728021642.VbEEiHE1fY9YNW6x-kjpDnG9R00gduZEhv_NtGfSQ4M@z \
--to=armedaviator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).