From: chilledfrogs <chilledfrogs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Steam can't find libpulsecommon.so
Date: Fri, 18 Dec 2020 19:05:08 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27260@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
New issue by chilledfrogs on void-packages repository
https://github.com/void-linux/void-packages/issues/27260
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.9.14_1 x86_64 GenuineIntel uptodate rrrrmdFFFFFFF
* package: `steam-1.0.0.68_1`
### Expected behavior
Steam launches
### Actual behavior
Fatal error on launch:
```
Error: You are missing the following 32-bit libraries, and Steam may not run:
libpulsecommon-14.0.so
```
Succeeded eventually by:
```
Failed to load steamui.so - dlerror(): libpulsecommon-14.0.so: wrong ELF class: ELFCLASS64
```
So it seems to somehow (only?) see the 64-bit shlib even though I have the 32-bit one as well in `/usr/lib32/pulseaudio/libpulsecommon-14.0.so`.
I can work around this in the meantime by prepending (well really just setting here since I don't have anything in this variable by default) `/usr/lib32/pulseaudio` to `LD_LIBRARY_PATH` when launching `steam` from the command line.
### Steps to reproduce the behavior
Just launch Steam
(Tried `steam --reset` just in case, no dice)
next reply other threads:[~2020-12-18 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 18:05 chilledfrogs [this message]
2020-12-18 18:26 ` Acetsetebos
2020-12-18 18:34 ` ericonr
2020-12-18 21:49 ` sburris0
2020-12-18 21:52 ` Johnnynator
2020-12-18 21:52 ` [ISSUE] [CLOSED] " Johnnynator
2020-12-18 21:52 ` Johnnynator
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27260@inbox.vuxu.org \
--to=chilledfrogs@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).