mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 13:02:03 +00:00
[GH-ISSUE #152] [Steam only] Wayland events: Broken pipe #98
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#98
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 @ClementVincent on GitHub (Nov 23, 2024).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/152
Hello !
I'm trying to launch the GOW steam container and stream it through Wolf (Sunshine) but facing an error. To be honest, I'm having a hard time pointing it out.
I see 4 errors in the logs :
[ERROR] [sway/main.c:62] !!! Proprietary Nvidia drivers are in use !!!--> From what I understand, Sway is compatible with Proprietary Nvidia drivers (although not supported), so we don't care
[error] Can't open RFKILL control device--> For Wifi (I guess we don't care here either)
JGdk-Message: 13:37:24.888: Error reading events from display: Broken pipe--> I suppose the result of a previous error in the stack
>fusermount3: fuse device not found, try 'modprobe fuse' firsterror: fuse init failed: Can't mount path /tmp/sockets/doc--> My best guess so far
I've seen users recommending to pass Fuse from host as a device but I'm not convinced. If anyone has an idea :)
Detailed logs
Additionnal information
Host OS : Unraid 7.0.0-beta4 (based Slackware 15.0 x86_64 (post 15.0 -current))
@salty2011 commented on GitHub (Nov 23, 2024):
Oh weird, haven't seen this one before.
Just to confirm, what method are you using for deploying wolf? You using the nvidia container toolkit or manual method
Also you able to attach your wolf config?
Lastly I noticed your using unraid7 beta, not sure if this version of unraid could be introducing some issues (I'm still using 6). But also does this system happen to have multiple gpu's?
Asking more to get better context of the setup
@ClementVincent commented on GitHub (Nov 23, 2024):
First, thank you for your time ! :)
Now, about your questions:
About the Unraid version, I updated it to 7.0.0-4 Beta to take advantage on the newly added support of User-space I/O HID subsystem (I had issues with this launching Wolf).
Finally, yes I'm having multiple GPUs (1 primary used for host and VMs & 1 secondary used for Dockers - currently used by 1 other container).
@ABeltramo commented on GitHub (Nov 23, 2024):
Thanks for all the info, just a couple more questions:
My guess is that the real issue here is:
Which hints at some issue with the GPU and/or drivers.
@ClementVincent commented on GitHub (Nov 24, 2024):
eglInitialize() failederror (it's weird that it's working with other app and not with steam though) but the container still crashingDetailed logs
Docker Run
@ABeltramo commented on GitHub (Nov 25, 2024):
Thanks for all the info,
failed to read Wayland events: Broken pipesounds like it could be an issue with our custom compositor (it should report something else in the logs though) or Sway.I think you can try a couple of things:
RUST_LOG=INFOto Wolf, this should log a few more info from our custom compositor, not sure if it'll show anything interesting but it's worth a try.config.tomlfor the Steam entry to:here's the default if you need it
Historically Gamescope had a few hiccups with Nvidia so we've defaulted to Sway but I think it's worth a try.
@ClementVincent commented on GitHub (Nov 30, 2024):
Just tested your ideas @ABeltramo, unforunately still not working. There is however an interesting error when using the Gamescope.
Logs with Sway (Rust log level to INFO)
Logs with Gamescope (Rust log level to INFO) :
@Murazaki commented on GitHub (Jan 14, 2025):
Got the same bug on Steam when upgrading to 565.77 and with latest wolf images.
@ABeltramo commented on GitHub (Jan 14, 2025):
@Murazaki please try to manually update to the latest Steam image with
Update Wolf too and if that doesn't fix it, open up a new issue and post your details.
This issue is 2 months old, there's been plenty of commits since then, and it probably doesn't apply to your case.
@jpuerto commented on GitHub (Jan 19, 2025):
I have the same issue using Arch with latest Wolf version and Nvidia container toolkit setup with driver version 565.77 on 2060 RTX. I choose that option as I had already a Ollama setup running without issues.
The streaming and Steam works with it, but the interface looks like not accelerated at all and everything feels with lag. From my tests, it seems like the EGL is somehow not working correctly, at least when using Sway and container toolkit solution.
After switch to docker manual installation, the Steam interface works great and I have tested a game and it seems to work at the expected performance.
The following error has gone from my setup, after switch to manual:
@ABeltramo commented on GitHub (Jan 21, 2025):
I'll definitely add a big red warning to the docs until I can figure out what's the underlying issue with the Container Toolkit. It's too hit-and-miss at the moment.
@Murazaki commented on GitHub (Jan 21, 2025):
I feel like we're just missing some important library to pass with the container toolkit, and I'm not sure which is it. This happened after installing 565.77 when it was working well with 550.127.05.
I might have lost an egl lib or something, (or it's a missing element from the nvidia driver).
@ClementVincent commented on GitHub (Feb 2, 2025):
Hello,
I tried again this morning with the latest updates. Bad news is that it's still crashing, good news however is that now I can go a little further.
The docker starts properly, it downloads the steam update, starts the configuration wizzard and then steam crashes : Steamwebhelper, a critical Steam component, is not responding. The Steam UI will not be usable.
I tried to delete Steam folder already and reinstall it with the same result. If anyone has an idea :)
@ABeltramo commented on GitHub (Feb 2, 2025):
This has been fixed for quite some time, make sure to update the Steam image with
and re-start Wolf
@ClementVincent commented on GitHub (Feb 2, 2025):
Yes, I did update the image before testing :
When starting the docker, steam checks the installation before crashing.
@ABeltramo commented on GitHub (Feb 2, 2025):
Can you post your Wolf logs with the env variable
WOLF_LOG_LEVEL=DEBUGfrom the start up until it crashes?@ClementVincent commented on GitHub (Feb 8, 2025):
Things are getting weird and wierder but at least now I'm pretty sure the issue is with steam itself. I'm still facing the Steamwebhelper error but, one out of 4-5 times, steam still boots-up.
Logs from systemmanager.txt (steam container) --> There is an error initiating Wayland
Logs from webhelper.txt (steam container) -->There is an error with SP shared JS Context, don't know if it means anything
Logs from Wolf Nvidia toolkit + Debug Mode --> nothing new
Steam logs from webhelper_gpu.txt: --> There are multiple problems found here, but not sure if it has a real impact
@Hotcooler commented on GitHub (Mar 15, 2025):
Just to update, probably the same thing happens with 1.17.5 container runtime + 570.86.15 driver. While 3D is software accelerated (and everything starts and moves), GPU encoding does get detected and works as expected. Did not really run with debug to confirm, but since pretty much only wolf and sway end up on the nvidia-smi listing, I'd say the same happens.
BTW for people on Ubuntu 22 if you want to build for the latest "server" driver (since for whatever reason only server ones are available for 570 or for that matter.. more recent than 550), you'll have to edit the dockerfile a bit and grab the driver from Nvidia: https://us.download.nvidia.com/tesla/570.86.15/NVIDIA-Linux-x86_64-570.86.15.run
Builds and runs just fine after that.
@Murazaki commented on GitHub (Mar 15, 2025):
Don't use this one, it is only a server GPU update. There's two more recent ones, one being a production build while this one and the previous are beta : https://download.nvidia.com/XFree86/Linux-x86_64/570.124.04/
Also you will have a better chance of Wolf running well with volumes lately. There's likely some bindings missing in nividia-container-toolkit that are critical to EGL for gaming.
@Hotcooler commented on GitHub (Mar 15, 2025):
Realistically server and non server have about zero difference, server one updates slower and that's probably it (I'd argue a naming problem, server should be akin to stable, and regular to edge/latest). I imagine like game ready and studio ones for windows (one updates a lot more than the other). That specific one is mentioned, since it's the only one available through apt/ubuntu-drivers/as a deb on Nvidia's site at least on 22.04. I linked that mostly so people know that server ones as Ubuntu calls them are in a different place on the site and you won't be able to build a container without changing some lines.
@Murazaki commented on GitHub (Mar 15, 2025):
Ubuntu does provide server versions because they intend it for those who use Ubuntu on GPU server farms. The issue is there's almost no update for basic users from the previous and it might not be even tested for them.
Here are the desktop ready version that corresponds to the same major version, it is visible on plucky repos (though it is not stable yet) :
https://packages.ubuntu.com/search?keywords=nvidia-driver&searchon=names&suite=plucky§ion=all
@KommanderKeen commented on GitHub (Jul 20, 2025):
@ABeltramo Now I'm on the manual nvidia (550) with GTX 1070, Firefox works but Steam is crashing and my logs have exactly the same problem as stated in the first post of this thread.
C[2025-07-20 15:18:33.033] [error] Can't open RFKILL control device
6Xwayland glamor: GBM Wayland interfaces not available
0Failed to initialize glamor, falling back to sw
(EE)
(EE) Backtrace:
<(EE) 0: Xwayland (0x5f4b28906000+0x1dfab2) [0x5f4b28ae5ab2]
<(EE) 1: Xwayland (0x5f4b28906000+0x1e6d55) [0x5f4b28aecd55]
R(EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x74d4c0510000+0x45810) [0x74d4c0555810]
X(EE) 3: /usr/nvidia/lib/libnvidia-egl-gbm.so.1 (0x74d4ba200000+0x1741) [0x74d4ba201741]
U(EE) 4: /usr/nvidia/lib/libEGL_nvidia.so.0 (0x74d4bf800000+0xadc00) [0x74d4bf8adc00]
U(EE) 5: /usr/nvidia/lib/libEGL_nvidia.so.0 (0x74d4bf800000+0x4ccec) [0x74d4bf84ccec]
S(EE) 6: /lib/x86_64-linux-gnu/libEGL.so.1 (0x74d4bfe6b000+0x7145) [0x74d4bfe72145]
](EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x74d4bf436000+0x74d0) [0x74d4bf43d4d0]
<(EE) 8: Xwayland (0x5f4b28906000+0x200586) [0x5f4b28b06586]
<(EE) 9: Xwayland (0x5f4b28906000+0x1f8d6f) [0x5f4b28afed6f]
<(EE) 10: Xwayland (0x5f4b28906000+0xef3bc) [0x5f4b289f53bc]
=(EE) 11: Xwayland (0x5f4b28906000+0x228931) [0x5f4b28b2e931]
<(EE) 12: Xwayland (0x5f4b28906000+0x43a64) [0x5f4b28949a64]
S(EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (0x74d4c0510000+0x2a338) [0x74d4c053a338]
S(EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x8b) [0x74d4c053a3fb]
<(EE) 15: Xwayland (0x5f4b28906000+0x46d25) [0x5f4b2894cd25]
(EE)
'(EE) Segmentation fault at address 0x0
(EE)
Fatal server error:
<(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
_00:00:00.299 [ERROR] [wlr] [xwayland/server.c:270] Xwayland startup failed, not setting up xwm
JGdk-Message: 15:18:33.112: Error reading events from display: Broken pipe
I also got this :
l00:00:00.002 [ERROR] [wlr] [backend/wayland/backend.c:261] drmGetDevices2 failed: No such file or directory
h00:00:00.002 [ERROR] [wlr] [render/wlr_renderer.c:249] drmGetDevices2 failed: No such file or directory
Does it say it tries to use a second devices other than the sole D128 I've put in my docker compose file ?
Because I have a second device D129 (GTX 1060) which is not given to the LXC where wolf is running.
It is passed to another LXC.
@ABeltramo commented on GitHub (Jul 20, 2025):
@KommanderKeen please don't crosspost, let's keep the discussion in https://github.com/games-on-whales/wolf/issues/230
@lifeofal3af commented on GitHub (Dec 24, 2025):
hi there! is there any update on the topic?