Github messages for voidlinux
 help / color / mirror / Atom feed
From: daerich <daerich@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] steam: update void specific troubleshooting
Date: Mon, 26 Jul 2021 22:59:10 +0200	[thread overview]
Message-ID: <20210726205910.dtENReq8OLDNqmBvJjtKLVOLxdctWCaWrSYfru0SsVk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31818@inbox.vuxu.org>

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

There is an updated pull request by daerich against master on the void-packages repository

https://github.com/daerich/void-packages daerich-steam-patch
https://github.com/void-linux/void-packages/pull/31818

steam: update void specific troubleshooting
Void's PAM configuration seems to limit file descriptors per process a little to aggressively leading to game crashes with the "eventfd: Too many open files" diagnostic.
The solution is according to Valve's upstream documentation on Proton's Wine fork to manually raise the limit in
 "/etc/security/limits.conf";
document that specific behavior.
Found by method of elimination by switching from ArchLinux to Void trying to play the same game with near identical configuration of both systems.
For 32bit Games it should also be advisable to pull 32bit audio libraries, preventing for example "This game requires a sound card in order to run" error when starting GTA IV.

<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/31818.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-daerich-steam-patch-31818.patch --]
[-- Type: text/x-diff, Size: 2348 bytes --]

From fd62a24fd67c239bcc2d798c5c730ae9507b6756 Mon Sep 17 00:00:00 2001
From: DaErich <daerich@sourceforge.net>
Date: Mon, 5 Jul 2021 14:52:36 +0200
Subject: [PATCH] steam: update void specific troubleshooting

---
 srcpkgs/steam/files/README.voidlinux | 11 +++++++++--
 srcpkgs/steam/template               |  4 ++--
 2 files changed, 11 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/steam/files/README.voidlinux b/srcpkgs/steam/files/README.voidlinux
index 35d1fe4798d0..025f58f445fb 100644
--- a/srcpkgs/steam/files/README.voidlinux
+++ b/srcpkgs/steam/files/README.voidlinux
@@ -28,8 +28,15 @@ installed for some games to function.
 If games are running slowly or not at all, or there are issues with network
 streaming, verify that your user belongs to the video group.
 
-If your audio is not working, try installing pulseaudio and
-alsa-plugins-pulseaudio.
+If your audio is not working, try installing pulseaudio,
+alsa-plugins-pulseaudio and their "<package>-32bit" equivalents.
+
+If you are using SteamPlay/Proton and the game crashes or hangs with error
+messages that include "eventfd: Too many open files", the number of open file
+descriptors per process is too low for proper Proton functionality.  In this
+case, consult limits.conf(5) and set a higher nofile limit for your user.  For
+more information, see the upstream documentation in the README.esync file from
+https://github.com/ValveSoftware/wine
 
 If you are encountering runtime errors, the Steam Ubuntu bootstrap tarball might
 be using an incompatible libstdc++ library. You can verify this by running the
diff --git a/srcpkgs/steam/template b/srcpkgs/steam/template
index 1574edc98dd1..5594b6a59793 100644
--- a/srcpkgs/steam/template
+++ b/srcpkgs/steam/template
@@ -1,6 +1,6 @@
 # Template file for 'steam'
 pkgname=steam
-version=1.0.0.70
+version=1.0.0.71
 revision=2
 archs="i686 x86_64"
 wrksrc=steam-launcher
@@ -11,7 +11,7 @@ maintainer="Andrew Benson <abenson+void@gmail.com>"
 license="custom: Proprietary license"
 homepage="https://steampowered.com/"
 distfiles="http://repo.steampowered.com/${pkgname}/pool/${pkgname}/s/${pkgname}/${pkgname}_${version}.tar.gz"
-checksum=9ff88a5778c7b00efb18f324d4cd0c282d5f438dad1201bc3e9822e3ff6a2dff
+checksum=39c33d1999f8cc6d4af696479e1d73eee2e93a217bc45887032e18b33535ca21
 repository=nonfree
 
 do_install() {

  parent reply	other threads:[~2021-07-26 20:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 12:57 [PR PATCH] steam:Update void specific troubleshooting(esync) daerich
2021-07-17  3:55 ` [PR REVIEW] " ericonr
2021-07-17  3:55 ` ericonr
2021-07-17  3:56 ` ericonr
2021-07-17  3:56 ` ericonr
2021-07-23 11:12 ` [PR PATCH] [Updated] steam: Update " daerich
2021-07-23 11:14 ` [PR PATCH] [Updated] steam: update void specific troubleshooting daerich
2021-07-23 11:17 ` daerich
2021-07-26 20:59 ` daerich [this message]
2021-07-26 21:00 ` [PR PATCH] [Updated] " daerich
2021-07-26 21:02 ` daerich
2021-07-26 21:03 ` daerich
2021-08-25  1:44 ` [PR PATCH] [Closed]: " abenson

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=20210726205910.dtENReq8OLDNqmBvJjtKLVOLxdctWCaWrSYfru0SsVk@z \
    --to=daerich@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).