Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Steam package requires multilibs glibc-32bit, mesa-32bit, and mesa-dri-32bit to run.
Date: Fri, 05 Feb 2021 04:31:23 +0100	[thread overview]
Message-ID: <20210205033123.CyYOaLTZ_9qSEt4aA3wSNCrl6qD7NF4QI_r311DayMw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20102@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

Closed issue by seisatsu on void-packages repository

https://github.com/void-linux/void-packages/issues/20102

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *Void 5.4.25_1 x86_64 AuthenticAMD notuptodate rrrrmdFFFFF*
* package:  
  *steam-1.0.0.61_7*

### Expected behavior
The `steam` executable should start after installing.

### Actual behavior
* When starting without glibc-32bit installed from multilibs, steam produces an error popup saying that the 32bit libc libraries are required to start.
* When starting without mesa-32bit or mesa-dri-32bit, a popup error warns that "glXChooseVisual failed".
* When starting with mesa-32bit but not mesa-dri-32bit, steam segfaults.

### Steps to reproduce the behavior
Install the steam package without installing the required multilibs packages, then attempt to run.

### Suggested solution
Move steam to the multilibs repository and require the necessary multilibs packages.

  parent reply	other threads:[~2021-02-05  3:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 20:20 [ISSUE] " seisatsu
2020-03-20  8:41 ` codingHahn
2020-03-25  0:59 ` Supersonic112
2020-03-25  9:14 ` codingHahn
2020-03-27  0:17 ` Supersonic112
2021-02-05  3:30 ` ericonr
2021-02-05  3:31 ` ericonr
2021-02-05  3:31 ` ericonr [this message]
2021-12-18 12:24 ` Vistaus
2021-12-18 14:14 ` Duncaen
2021-12-18 14:14 ` Duncaen

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=20210205033123.CyYOaLTZ_9qSEt4aA3wSNCrl6qD7NF4QI_r311DayMw@z \
    --to=ericonr@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).