From: TeusLollo <TeusLollo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: steam-for-linux largely non-functional after new electron-based beta update was mainlined
Date: Thu, 02 Nov 2023 21:53:40 +0100 [thread overview]
Message-ID: <20231102205340.CABr-xxMF3pVPmQwKpz9HJIycSgCixseCUO8qfW-ASI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46649@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
New comment by TeusLollo on void-packages repository
https://github.com/void-linux/void-packages/issues/46649#issuecomment-1791523149
Comment:
OK, I just finished testing with `steam-for-linux` native on Void (Previously I had only tested flatpak), and:
Yes, it now works perfectly, given update https://github.com/void-linux/void-packages/commit/42207dee813d9522f81506c1922fd5e5f9bd95b4 (`mesa-23.2.1_2`)
Thus, currently `steam-for-linux` as Flatpak version still produces the abovementioned error due to packaging the older `mesa` version (`mesa-23.1.x_x`).
Native `steam-for-linux` with https://github.com/void-linux/void-packages/commit/42207dee813d9522f81506c1922fd5e5f9bd95b4 (`mesa-23.2.1_2`) is however fine.
Aside from `steam-for-linux` on flatpak not being a problem of the Void Team, it's also likely that this error will be fixed once flatpak updates its own `mesa` version.
Closing this as solved thanks to the recent `mesa` update, but anyone is free to reopen in case this "beatiful" electron app throws more problem in the future.
next prev parent reply other threads:[~2023-11-02 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 23:34 [ISSUE] " TeusLollo
2023-10-12 23:35 ` TeusLollo
2023-10-12 23:40 ` TeusLollo
2023-11-02 20:06 ` TeusLollo
2023-11-02 20:17 ` TeusLollo
2023-11-02 20:53 ` TeusLollo [this message]
2023-11-02 20:53 ` [ISSUE] [CLOSED] " TeusLollo
2023-11-02 21:25 ` TeusLollo
2023-11-02 21:25 ` TeusLollo
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=20231102205340.CABr-xxMF3pVPmQwKpz9HJIycSgCixseCUO8qfW-ASI@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).