From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] steam:Update void specific troubleshooting(esync)
Date: Sat, 17 Jul 2021 05:55:04 +0200 [thread overview]
Message-ID: <20210717035504.V5pL5KNaId3tX6cXDeMHLcMgJ8czkyNZ2-ddF_dXj2E@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: 793 bytes --]
New review comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/31818#discussion_r671604144
Comment:
```suggestion
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 complete Proton functionality.
In this case, consult limits.conf(5) and set a higher nofile limit for your user.
For more information, see upstream documentation in the README.esync file from
https://github.com/ValveSoftware/wine
```
I think we can be more concise. And please fix line breaks so all lines have around the same length (in VIM you can do this by selecting the block and pressing `qg` while still in visual mode).
next prev parent reply other threads:[~2021-07-17 3:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 12:57 [PR PATCH] " daerich
2021-07-17 3:55 ` [PR REVIEW] " ericonr
2021-07-17 3:55 ` ericonr [this message]
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 ` [PR PATCH] [Updated] " daerich
2021-07-26 21:00 ` 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=20210717035504.V5pL5KNaId3tX6cXDeMHLcMgJ8czkyNZ2-ddF_dXj2E@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).