[GH-ISSUE #258] Wolf container crashes immediately upon pressing controller button #178

New issue

Closed

opened 2026-10-15 12:57:45 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-15 12:57:45 +00:00

Owner

Originally created by @willprice on GitHub (Sep 24, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/258

Hi folks,

First, thanks for putting time into such an awesome project!

I'm a newbie to wolf, and I'm trying to get setup. I've got as far as running wolf on my home server and have successfully connected to it from a number of devices. It seems that regardless of which device I use (virtual controller on android moonlight client, or PS5 controller on my chromecast client/android phone), any non-mouse input causes wolf to immediately crash.

Here are the logs I get (from docker logs -f wolf):

22:47:14.066911056 WARN  | Received MOUSE_MOVE_REL_PACKET but no mouse device is present
22:47:14.082716672 WARN  | Received MOUSE_MOVE_REL_PACKET but no mouse device is present
0:03:42.860837798     1 0x7bd48c01ccd0 WARN                basesink gstbasesink.c:1248:gst_base_sink_query_latency:<18095082255011644597_video> warning: Pipeline construction is invalid, please add queues.
0:03:42.860858118     1 0x7bd48c01ccd0 WARN                basesink gstbasesink.c:1248:gst_base_sink_query_latency:<18095082255011644597_video> warning: Not enough buffering available for the processing deadline of 0:00:00.020000000, add enough queues to buffer  0:00:00.020000000 additional data. Shortening processing latency to 0:00:00.000000000.
22:47:14.164622955 INFO  | Wayland display ready, listening on: wayland-1
2025-09-24T22:47:14.180194Z  WARN waylanddisplaycore::comp: Error during GetRenderDevice: No GPU device for given DRM node
0:03:42.879486495     1 0x7bd478001030 WARN               vaencoder gstvaencoder.c:750:gst_va_encoder_get_prediction_direction:<vaencoder2> Driver does not support query prediction direction
0:03:42.879509195     1 0x7bd478001030 WARN               vaencoder gstvaencoder.c:839:gst_va_encoder_has_trellis:<vaencoder2> Driver does not support trellis
22:47:14.190353045 WARN  | [DOCKER] Container WolfPegasus_18095082255011644597 already present, removing first
0:03:42.907164407     1 0x7bd478001030 WARN                 basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc0> segment format mismatched, ignore
22:47:14.568499816 INFO  | [DOCKER] Starting container: /WolfPegasus_18095082255011644597
0:03:44.390928787     1 0x7bd4780015f0 WARN                 basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc1> segment format mismatched, ignore
22:47:19.387871054 INFO  | Creating Xbox joypad for controller 0
22:47:19.391537615 ERROR | Failed to create Xbox One joypad: No such device
EVP_EncryptInit_ex failed
EVP_CIPHER_CTX_set_padding failed
EVP_EncryptInit_ex failed
EVP_EncryptUpdate failed
EVP_EncryptFinal_ex failed
EVP_EncryptInit_ex failed
EVP_CIPHER_CTX_set_padding failed
EVP_EncryptInit_ex failed
EVP_EncryptUpdate failed
EVP_EncryptFinal_ex failed
EVP_EncryptInit_ex failed
EVP_CIPHER_CTX_set_padding failed
EVP_EncryptInit_ex failed
EVP_EncryptUpdate failed
EVP_EncryptFinal_ex failed
EVP_EncryptInit_ex failed
EVP_CIPHER_CTX_set_padding failed
EVP_EncryptInit_ex failed
EVP_EncryptUpdate failed
EVP_EncryptFinal_ex failed
EVP_EncryptInit_ex failed
EVP_CIPHER_CTX_set_padding failed
EVP_EncryptInit_ex failed
EVP_EncryptUpdate failed
EVP_EncryptFinal_ex failed
EVP_EncryptInit_ex failed
EVP_CIPHER_CTX_set_padding failed

$ docker images | grep wolf
ghcr.io/games-on-whales/wolf            stable    fe62ab9f16ec   6 days ago      2.06GB

For what it's worth, I tried running with WOLF_LOG_LEVEL=DEBUG set, but didn't get any additional useful logging messages out.

Originally created by @willprice on GitHub (Sep 24, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/258 Hi folks, First, thanks for putting time into such an awesome project! I'm a newbie to wolf, and I'm trying to get setup. I've got as far as running wolf on my home server and have successfully connected to it from a number of devices. It seems that regardless of which device I use (virtual controller on android moonlight client, or PS5 controller on my chromecast client/android phone), any non-mouse input causes wolf to immediately crash. Here are the logs I get (from `docker logs -f wolf`): ``` 22:47:14.066911056 WARN | Received MOUSE_MOVE_REL_PACKET but no mouse device is present 22:47:14.082716672 WARN | Received MOUSE_MOVE_REL_PACKET but no mouse device is present 0:03:42.860837798 1 0x7bd48c01ccd0 WARN basesink gstbasesink.c:1248:gst_base_sink_query_latency:<18095082255011644597_video> warning: Pipeline construction is invalid, please add queues. 0:03:42.860858118 1 0x7bd48c01ccd0 WARN basesink gstbasesink.c:1248:gst_base_sink_query_latency:<18095082255011644597_video> warning: Not enough buffering available for the processing deadline of 0:00:00.020000000, add enough queues to buffer 0:00:00.020000000 additional data. Shortening processing latency to 0:00:00.000000000. 22:47:14.164622955 INFO | Wayland display ready, listening on: wayland-1 2025-09-24T22:47:14.180194Z WARN waylanddisplaycore::comp: Error during GetRenderDevice: No GPU device for given DRM node 0:03:42.879486495 1 0x7bd478001030 WARN vaencoder gstvaencoder.c:750:gst_va_encoder_get_prediction_direction:<vaencoder2> Driver does not support query prediction direction 0:03:42.879509195 1 0x7bd478001030 WARN vaencoder gstvaencoder.c:839:gst_va_encoder_has_trellis:<vaencoder2> Driver does not support trellis 22:47:14.190353045 WARN | [DOCKER] Container WolfPegasus_18095082255011644597 already present, removing first 0:03:42.907164407 1 0x7bd478001030 WARN basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc0> segment format mismatched, ignore 22:47:14.568499816 INFO | [DOCKER] Starting container: /WolfPegasus_18095082255011644597 0:03:44.390928787 1 0x7bd4780015f0 WARN basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc1> segment format mismatched, ignore 22:47:19.387871054 INFO | Creating Xbox joypad for controller 0 22:47:19.391537615 ERROR | Failed to create Xbox One joypad: No such device EVP_EncryptInit_ex failed EVP_CIPHER_CTX_set_padding failed EVP_EncryptInit_ex failed EVP_EncryptUpdate failed EVP_EncryptFinal_ex failed EVP_EncryptInit_ex failed EVP_CIPHER_CTX_set_padding failed EVP_EncryptInit_ex failed EVP_EncryptUpdate failed EVP_EncryptFinal_ex failed EVP_EncryptInit_ex failed EVP_CIPHER_CTX_set_padding failed EVP_EncryptInit_ex failed EVP_EncryptUpdate failed EVP_EncryptFinal_ex failed EVP_EncryptInit_ex failed EVP_CIPHER_CTX_set_padding failed EVP_EncryptInit_ex failed EVP_EncryptUpdate failed EVP_EncryptFinal_ex failed EVP_EncryptInit_ex failed EVP_CIPHER_CTX_set_padding failed EVP_EncryptInit_ex failed EVP_EncryptUpdate failed EVP_EncryptFinal_ex failed EVP_EncryptInit_ex failed EVP_CIPHER_CTX_set_padding failed ``` ``` $ docker images | grep wolf ghcr.io/games-on-whales/wolf stable fe62ab9f16ec 6 days ago 2.06GB ``` For what it's worth, I tried running with `WOLF_LOG_LEVEL=DEBUG` set, but didn't get any additional useful logging messages out.

bsakaguchi closed this issue

2026-10-15 12:57:45 +00:00

bsakaguchi commented

2026-10-15 12:57:46 +00:00

Author

Owner

@willprice commented on GitHub (Sep 25, 2025):

I did an upgrade on the host box (arch) and rebooted and now it's working!

@willprice commented on GitHub (Sep 25, 2025): I did an upgrade on the host box (arch) and rebooted and now it's working!

bsakaguchi commented

2026-10-15 12:57:46 +00:00

Author

Owner

@ABeltramo commented on GitHub (Sep 25, 2025):

The issue here is most likely related to the kernel module uinput and the corresponding udev rules that we have in the quickstart guide. Either the module was not loaded or the rules were not applied and so rebooting made everything fall in place.

Feel free to re-open if you encounter it again though.

@ABeltramo commented on GitHub (Sep 25, 2025): The issue here is most likely related to the kernel module `uinput` and the corresponding `udev` rules that we have in the quickstart guide. Either the module was not loaded or the rules were not applied and so rebooting made everything fall in place. Feel free to re-open if you encounter it again though.