Skip to content
This repository has been archived by the owner on Aug 3, 2024. It is now read-only.

Troubleshooting

Jump to bottom
galister edited this page Jul 1, 2023 · 34 revisions

SocketException (98): Address already in use

You may have started WlxOverlay while it's already running somewhere else.

Remember; WlxOverlay will be started by SteamVR automatically!

It's not impossible that something else is using the port. Check using lsof -i :42069

If you need to run WlxOverlay by hand (to see logs, etc), clean up any running instances first:

pkill -f WlxOverlay

Failed to connect to wayland display server when on X11

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.

ioctl returned -1 on startup

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.

Lasers are not visible

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)

GLFW Init failed, PlatformError

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.

Wayland: Screens are black

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, DP-2, HDMI-1, anything else with capital letters -> Wayland

Method 2: Look for Wayland detected. in the logs

If you're sure that you're not on XWayland, the capture might have issues. Try switching to software capture by setting wayland_capture: pw-fallback in your config.yaml.

BadAlloc on eglCreateImage

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.

Reaching out

Hop on to this Discord Server and poke me if you need more help.

There is also a Matrix Space here: #linux-vr-adventures:matrix.org

Clone this wiki locally