From: TeusLollo <TeusLollo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: update mesa
Date: Thu, 05 Oct 2023 19:02:25 +0200 [thread overview]
Message-ID: <20231005170225.ke4FRqrqX7_SbQjzRgyOWFVokKZFJIxcPJSxjOGgg_0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46246@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
New comment by TeusLollo on void-packages repository
https://github.com/void-linux/void-packages/issues/46246#issuecomment-1749319103
Comment:
I haven't been able to run the Steam client (Flatpak version) at all since they switched to their new electron-based interface (Not surprising).
Indeed, that interface seems to be producing myriads of problems:
https://github.com/ValveSoftware/steam-for-linux/issues/9630
https://github.com/ValveSoftware/steam-for-linux/issues/9383
https://github.com/ValveSoftware/steam-for-linux/issues/9984
https://github.com/ValveSoftware/steam-for-linux/issues/10001
https://github.com/ValveSoftware/steam-for-linux/issues/8667
https://github.com/ValveSoftware/steam-runtime/issues/403
https://github.com/ValveSoftware/steam-for-linux/issues/9077
Not sure if a flatpak problem, a Void packaging issue, or some dependency missing.
I have tried disabling hardware acceleration, to not avail.
I regularly get a:
`
amdgpu_device_initialize: amdgpu_get_auth (1) failed (-1)
amdgpu: amdgpu_device_initialize failed.
libGL error: glx: failed to create dri3 screen
libGL error: failed to load driver: radeonsi
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 336
steam-runtime-launcher-service[336]: E: Unable to acquire bus name "com.steampowered.PressureVessel.LaunchAlongsideSteam"
amdgpu_device_initialize: amdgpu_get_auth (1) failed (-1)
amdgpu: amdgpu_device_initialize failed.
libGL error: glx: failed to create dri3 screen
libGL error: failed to load driver: radeonsi
`
Not sure if related, though. The new client seems to be a bug-ridden mess.
@darkralts Does the Steam client work on your end since they switched to the new electron-based one?
next prev parent reply other threads:[~2023-10-05 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 14:14 [ISSUE] " darkralts
2023-09-26 0:20 ` zlice
2023-10-05 17:02 ` TeusLollo [this message]
2023-10-07 9:40 ` SpidFightFR
2023-10-11 0:44 ` TeusLollo
2023-10-11 6:16 ` SpidFightFR
2023-10-11 6:22 ` SpidFightFR
2023-11-02 20:08 ` TeusLollo
2023-11-02 20:11 ` SpidFightFR
2023-11-02 20:16 ` TeusLollo
2023-11-02 20:45 ` TeusLollo
2023-11-02 20:45 ` TeusLollo
2023-11-02 20:54 ` TeusLollo
2023-11-02 21:26 ` TeusLollo
2023-12-07 3:40 ` [ISSUE] [CLOSED] " ahesford
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=20231005170225.ke4FRqrqX7_SbQjzRgyOWFVokKZFJIxcPJSxjOGgg_0@z \
--to=teuslollo@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).