Supervisor Tests gets in infinite loop "waiting for child to quit"
Describe the bug
gamemoded -t has "waiting for child to quit" endless loop under Supervisor tests on Slackware 15.0.
: Loading config
Loading config file [/usr/share/gamemode/gamemode.ini]
: Running tests
:: Basic client tests
:: Passed
:: Dual client tests
gamemode request succeeded and is active
Quitting by request...
:: Passed
:: Gamemoderun and reaper thread tests
...Waiting for child to quit...
...Waiting for reaper thread (reaper_frequency set to 5 seconds)...
:: Passed
:: Supervisor tests
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
...Waiting for child to quit...
^C
To Reproduce Installed with Slackware 15.0 and setting meson option for elogind. Using default gamemode.ini.
Expected behavior Complete the test without error (or at least not get in an endless loop and provide an error).
System Info (please complete the following information):
- OS and version: Slackware 15.0
- GameMode Version 1.7 & latest git commit (8cfc3453123c9b29b54ba12e7d6506d56a928ae4)
Additional context GameMode itself seems to run fine.
I'm willing to provide my build scripts/options if needed.
I'm willing to provide my build scripts/options if needed.
If interested, the build script is now available to view here.
I'm seeing the same thing on Arch Linux with version 1.8.1-1. Are there any debug variables or flags to get more info?
This is no longer a problem for me on Arch, but I have now idea how or when.
:: Supervisor tests
:: Passed