From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Gamemode is missing a build option that makes renice work
Date: Fri, 05 Aug 2022 19:37:42 +0200 [thread overview]
Message-ID: <20220805173742.6QpX_Xfk0sZIHD_4Guy5C3Y7e4jOFsYMDYJbYOooSL8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38362@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Closed issue by itsdeadguy on void-packages repository
https://github.com/void-linux/void-packages/issues/38362
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.14_1 x86_64
### Package(s) Affected
gamemode-1.6.1_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://github.com/FeralInteractive/gamemode/issues/335#issuecomment-997211721
https://github.com/FeralInteractive/gamemode/issues/291
### Expected behaviour
Gamemode's renice configuration works as described in `man gamemoded`. See also the [archwiki entry on gamemode](https://wiki.archlinux.org/title/Gamemode)
### Actual behaviour
Gamemode's renice configuration errors out on account of a missing file and a build option.
### Steps to reproduce
1. Install gamemode.
2. Copy the configuration file (`gamemode.ini`) from the default path to `~/.config`.
3. Edit the configuration file changing the `renice` option from the default vale `0` to, for example, `10`.
4. run `gamemode -t` and notice the errors.
I tried pulling the file `etc/security/limits.d/10-gamemode.conf` from gamemode's source on github, creating the gamemode group and adding my user to it, but a reboot later `gamemode -t` still produces the same errors.
prev parent reply other threads:[~2022-08-05 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 21:31 [ISSUE] " itsdeadguy
2022-08-05 17:37 ` classabbyamp [this message]
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=20220805173742.6QpX_Xfk0sZIHD_4Guy5C3Y7e4jOFsYMDYJbYOooSL8@z \
--to=classabbyamp@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).