Github messages for voidlinux
 help / color / mirror / Atom feed
From: Lolzen <Lolzen@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 10:45:18 +0200	[thread overview]
Message-ID: <20210728084518.7fFRysHtEIW99tqc7_5yopp0u7-pZDpoU8Bwirr4e7U@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: 1182 bytes --]

New comment by Lolzen on void-packages repository

https://github.com/void-linux/void-packages/issues/32222#issuecomment-888130363

Comment:
I did an system update (seemingly unrelated) about an hour ago

> Name         Action    Version           New version            Download size
> dtc          update    1.6.0_1           1.6.1_1                99KB 
> libldns      update    1.7.1_4           1.7.1_5                164KB 
> libpoppler   install   -                 21.07.0_1              1054KB 
> poppler-glib update    21.05.0_1         21.07.0_1              152KB 
> poppler-qt5  update    21.05.0_1         21.07.0_1              177KB 
> python3-pip  update    21.1.3_1          21.2.1_1               1127KB 
> webkit2gtk   update    2.32.1_2          2.32.3_1               24MB 

I could launch Sea of Thieves and played it for about 15-20 minutes. GTAV still had the error stating to verify the game files, which i once again did. But the error in question was not in the logs anymore, so i rebuilt the compdata and just launched GTAV aswell.

Other than that i have not changed a single thing, using steam and nvidia packages from XBPS repositories.

  parent reply	other threads:[~2021-07-28  8:45 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
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 [this message]
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=20210728084518.7fFRysHtEIW99tqc7_5yopp0u7-pZDpoU8Bwirr4e7U@z \
    --to=lolzen@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).