-
Notifications
You must be signed in to change notification settings - Fork 6
Troubleshooting
Because some SteamVR versions only work with WAYLAND_DISPLAY
unset, WlxOverlay doesn't rely on WAYLAND_DISPLAY
.
Instead, it will try and discover the wayland socket itself at $XDG_RUNTIME_DIR/wayland-*
Some desktop environments are known not to clear this wayland socket after switching wayland → X11 without a reboot. In these cases, it's ok to remove this file.
Ensure that your user has access to uinput.
This is usually as simple as adding yourself to the input group:
sudo usermod -a -G input $USER
You will likely need to reboot or restart your desktop session.
I have heard of a single case when no matter what we've tried the lasers wouldn't show.
If you run into this, try enabling the fallback_cursors
option in the config.yaml
.
Also please reach out as I want to know more about this issue. (Discord link below)
The error message will look like this:
Silk.NET.GLFW.GlfwException: GLFW Init failed, PlatformError: Wayland: Failed to connect to display
Solution:
Your distro should provide separate packages for glfw-wayland
and glfw-x11
, which conflict.
Make sure that you're using the X11 package when running under X11 and the Wayland package when running under Wayland.
WlxOverlay needs to interface with your Wayland compositor directly, and attempts to run it via XWayland will result in black screens.
Verify you're not running under XWayland
Method 1: Check the screen names on your watch.
-
Scr 1
,Scr 2
, etc -> Xorg screens (XWayland) -
Default
or anything with capital letters -> Wayland
Method 2: Look for Wayland detected.
in the logs
Happens when using PipeWire GPU capture.
Try switching to software capture by setting wayland_capture: pw-fallback
in your config.yaml
.
Also please provide us logs and info of your desktop environment on Discord or in a ticket, so that we can look into it.
Hop on to this Discord Server and poke me if you need more help.