mirror of
https://github.com/games-on-whales/unraid-plugin.git
synced 2026-10-15 13:02:00 +00:00
[GH-ISSUE #57] Gamepad Input from Applications Leaking into WolfUI #19
Labels
No labels
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/unraid-plugin#19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @thewave1408 on GitHub (Jun 28, 2026).
Original GitHub issue: https://github.com/games-on-whales/unraid-plugin/issues/57
I followed https://github.com/games-on-whales/wolf/issues/435 closely and as per the recommendations in that thread, updating the Wolf deployment seemed to solve the issue. However, after re-pulling the images today the issue seems to have resurfaced. Symptoms are the same as they were in the original issue - when using a gamepad and playing a game I will occasionally be kicked back into/out of Wolf UI or into a different container (like Lutris)
There were some commits a few days ago https://github.com/games-on-whales/wolf/pull/445 that may have contributed.
@thewave1408 commented on GitHub (Jul 1, 2026):
Repulled the images today after changing nothing and no longer experiencing the input leak. Sorry to bother...
@thewave1408 commented on GitHub (Jul 6, 2026):
SO, I stopped the entire wolf stack on Unraid today and deleted every docker image I had downloaded, so I pulled every image from scratch today. After starting Wolf UI and then Steam I experienced the same issue - an input leak into the Wolf UI container. It is very difficult to pin down exactly how to reproduce this, but in my experience over the past few weeks I will experience this input leak for a period of time, and then after I accidentally exit Wolf UI (while playing a steam game, via the input leak) controller input will no longer work in Wolf UI (and often steam big picture). The steam container seems to have no issue with controller input once I'm in a game. I'll attach some logs from Wolf:
I want to note a few things here:
@JBailes commented on GitHub (Jul 6, 2026):
Please launch where you are having trouble with, and run:
docker ps # find the app container Wolf spawned
docker exec -it app-container-id-from-previous-step bash
GPU
ls -l /dev/dri # render node present?
vulkaninfo --summary # GPU listed, correct driver — not "llvmpipe"/lavapipe
nvidia-smi # NVIDIA only
glxinfo -B | grep -i renderer # if mesa-utils present
Input (Wolf hot-plugs these via fake-udev)
ls -l /dev/input/ # event devices appear when a controller connects
cat /proc/bus/input/devices # should list Wolf's virtual gamepad/mouse/kbd
Wayland / display
echo $WAYLAND_DISPLAY # wolf sets this; socket should exist
ls -l $XDG_RUNTIME_DIR # wayland socket present
Audio
echo $PULSE_SERVER; pactl info # audio sink reachable
@JBailes commented on GitHub (Jul 6, 2026):
https://github.com/games-on-whales/wolf/pull/455
Wolf has a PR in for this, both to fix this and allow us to easily diagnose it in the future. Watch #455
@JesterEE commented on GitHub (Jul 17, 2026):
Once https://github.com/games-on-whales/wolf/pull/455 is accepted, scripts/deploy.sh will need to be updated to the new udev rules outlined in the PR. If wolf/85-wolf.rules is retained in the upstream dependency, it may be better to pull the required file directly from the repo to sync these requirements as they evolve over time instead of hardcoding them here.
github.com/games-on-whales/unraid-plugin@37e8531a7c/scripts/deploy.sh (L71)@JBailes commented on GitHub (Aug 9, 2026):
Update pushed to fix this iwth the merging of #455
@JBailes commented on GitHub (Aug 19, 2026):
@thewave1408 @JesterEE I expect this to be fixed, if either of you can verify?
@thewave1408 commented on GitHub (Aug 24, 2026):
Unfortunately Wolf isn't really functional for me at this time due to the other issue, so I'm not able to test
@thewave1408 commented on GitHub (Sep 7, 2026):
Had a chance to do a bit of testing and as best I can tell I think the issue is resolved!