search

games-on-whales / wolf

Stream virtual desktops and games running in Docker
https://games-on-whales.github.io/wolf/stable/
MIT License
292 stars 20 forks source link

pulseaudio container errors #40

Closed solipsist01 closed 8 months ago

solipsist01 commented 10 months ago

I'm happily running gow for months now :) I thought, it would be nice to have multiple applications, and also work without a dummy plug, so i'm giving wolf a spin.

I'm running debian bookworm

root@debian:/# uname -a
Linux debian 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-1 (2023-07-14) x86_64 GNU/Linux

Consider the following compose (just a copy / paste from the docs :))

version: "3.8"
services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    environment:
      - XDG_RUNTIME_DIR=/tmp/sockets
      - HOST_APPS_STATE_FOLDER=/etc/wolf
    volumes:
      - /etc/wolf/wolf:/wolf/cfg
      - /tmp/sockets:/tmp/sockets:rw
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /dev/shm:/dev/shm:rw
      - /dev/input:/dev/input:rw
      - /run/udev:/run/udev:rw
    devices:
      - /dev/dri
      - /dev/uinput
    device_cgroup_rules:
      - 'c 13:* rmw'
    network_mode: host
    restart: unless-stopped

Wolf starts. i can connect with moonlight etc, and also the pin stuff worked :)

the logging from the wolf container looks like this:


[2023-08-30 06:31:17] 
[2023-08-30 06:31:17] [ /etc/cont-init.d/10-setup_user.sh: executing... ]
[2023-08-30 06:31:17] **** Configure default user ****
[2023-08-30 06:31:17] Container running as root. Nothing to do.
[2023-08-30 06:31:17] DONE
[2023-08-30 06:31:17] 
[2023-08-30 06:31:17] [ /etc/cont-init.d/15-setup_devices.sh: executing... ]
[2023-08-30 06:31:17] **** Configure devices ****
[2023-08-30 06:31:17] Exec device groups
[2023-08-30 06:31:17] Adding user 'root' to groups: gow-gid-102,root
[2023-08-30 06:31:17] DONE
[2023-08-30 06:31:17] 
[2023-08-30 06:31:17] [ /etc/cont-init.d/30-nvidia.sh: executing... ]
[2023-08-30 06:31:17] 
[2023-08-30 06:31:17] 
[2023-08-30 06:31:17] [ /etc/cont-init.d/init-gamescope.sh: executing... ]
[2023-08-30 06:31:17] **** Setting up Gamescope ****
[2023-08-30 06:31:17] Launching the container's startup script as user 'root'
0:00:00.008668538   121 0x55d6344aa520 WARN              cudaloader gstcudaloader.c:169:gst_cuda_load_library: Could not open library libcuda.so.1, libcuda.so.1: cannot open shared object file: No such file or directory
0:00:00.008682509   121 0x55d6344aa520 WARN                 nvcodec plugin.c:93:plugin_init: Failed to load cuda library
0:00:00.049087777   121 0x55d6344aa520 WARN                 default ges-meta-container.c:236:_set_value:<GESAsset@0x55d634d49f90> Could not set value on item: format-version
0:00:00.049107117   121 0x55d6344aa520 WARN                 default ges-meta-container.c:236:_set_value:<GESAsset@0x55d634830a70> Could not set value on item: format-version
0:00:00.049114952   121 0x55d6344aa520 WARN                 default ges-meta-container.c:236:_set_value:<GESAsset@0x55d634831150> Could not set value on item: format-version
0:00:00.049343376   121 0x55d6344aa520 WARN               structure gststructure.c:2334:priv_gst_structure_parse_fields: Failed to find delimiter, r=mimetype
0:00:00.057037098   121 0x55d6344aa520 WARN      GST_PLUGIN_LOADING gstplugin.c:534:gst_plugin_register_func: plugin "/usr/local/lib/x86_64-linux-gnu/gstreamer-1.0/validate/libgstvalidatessim.so" failed to initialise
0:00:00.068276825   121 0x55d6344aa520 WARN          adaptivedemux2 gstadaptivedemuxelement.c:41:adaptivedemux2_base_element_init: Failed to load libsoup library
0:00:00.068374330   121 0x55d6344aa520 WARN          adaptivedemux2 gstadaptivedemuxelement.c:41:adaptivedemux2_base_element_init: Failed to load libsoup library
0:00:00.068480866   121 0x55d6344aa520 WARN          adaptivedemux2 gstadaptivedemuxelement.c:41:adaptivedemux2_base_element_init: Failed to load libsoup library
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
0:00:00.116867793   121 0x55d6344aa520 WARN                 default gstvaapi.c:231:plugin_init: Cannot create a VA display
0:00:00.118825913   121 0x55d6344aa520 WARN      GST_PLUGIN_LOADING gstplugin.c:534:gst_plugin_register_func: plugin "/usr/local/lib/x86_64-linux-gnu/gstreamer-1.0/validate/libgstvalidatessim.so" failed to initialise
06:31:17.883901064 INFO  | Gstreamer version: 1.22.0-0
06:31:17.884551159 INFO  | Reading config file from: /wolf/cfg/config.toml
06:31:17.884593355 WARN  | Unable to open config file: /wolf/cfg/config.toml, creating one using defaults
0:00:00.150018113     1 0x5611c102ea90 WARN     GST_ELEMENT_FACTORY gstelementfactory.c:712:gst_element_factory_make_with_properties: no such element factory "nvh264enc"!
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
06:31:17.943254116 INFO  | Selected H264 encoder: qsv
0:00:00.199723112     1 0x5611c102ea90 WARN     GST_ELEMENT_FACTORY gstelementfactory.c:712:gst_element_factory_make_with_properties: no such element factory "nvh265enc"!
06:31:17.943390422 INFO  | Selected HEVC encoder: qsv
06:31:17.943588567 INFO  | x509 certificates not present, generating: /wolf/cfg/cert.pem /wolf/cfg/key.pem
06:31:18.001459867 INFO  | RTSP server started on port: 48010
06:31:18.001502513 INFO  | HTTP server listening on port: 47989 
06:31:18.001517984 INFO  | RTP server started on port: 48000
06:31:18.001514812 INFO  | RTP server started on port: 47998
06:31:18.001574178 INFO  | Control server started on port: 47999
06:31:18.001741509 WARN  | [PULSE] Unable to connect, Access denied
06:31:18.001785872 INFO  | Starting PulseAudio docker container
06:31:18.002461215 INFO  | HTTPS server listening on port: 47984

Seems that wolf cannot connect to pulseaudio. This is the log listing of the pulseaudio container.


[2023-08-30 06:31:18] 
[2023-08-30 06:31:18] [ /etc/cont-init.d/10-setup_user.sh: executing... ]
[2023-08-30 06:31:18] **** Configure default user ****
[2023-08-30 06:31:18] Container running as root. Nothing to do.
[2023-08-30 06:31:18] DONE
[2023-08-30 06:31:18] 
[2023-08-30 06:31:18] [ /etc/cont-init.d/15-setup_devices.sh: executing... ]
[2023-08-30 06:31:18] **** Configure devices ****
[2023-08-30 06:31:18] Exec device groups
[2023-08-30 06:31:18] Not modifying user groups ()
[2023-08-30 06:31:18] DONE
[2023-08-30 06:31:18] 
[2023-08-30 06:31:18] [ /etc/cont-init.d/30-nvidia.sh: executing... ]
[2023-08-30 06:31:18] 
[2023-08-30 06:31:18] Launching the container's startup script as user 'root'
[2023-08-30 06:31:18] Removing all files from /root/.config/pulse
[2023-08-30 06:31:18] Starting pulseaudio
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
W: [pulseaudio] authkey.c: Failed to open cookie file '/root/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key '/root/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to open cookie file '/root/.pulse-cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key '/root/.pulse-cookie': No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

The reason wolf cannot connect to pulse audio, is because the pulseaudio container doesn't seem to run properly ? The container does keep running, however.

When i run the firefox app from moonlight, this is the error log from the Wolf container:


06:44:35.315159515 INFO  | Starting container: /WolfFirefox_7518890674366070471
0:01:48.975311740     1 0x7fcd5c00c800 WARN                   pulse pulsesrc.c:1016:gst_pulsesrc_open:<pulsesrc1> error: Failed to connect: Connection refused
06:44:35.581917610 ERROR | [GSTREAMER] Pipeline error: Failed to connect: Connection refused
0:01:49.127863038     1 0x7fcd5c00c800 WARN                   pulse pulsesrc.c:1016:gst_pulsesrc_open:<pulsesrc1> error: Failed to connect: Connection refused
0:01:49.128217085     1 0x7fcd5c00c800 WARN                   pulse pulsesrc.c:1016:gst_pulsesrc_open:<pulsesrc1> error: Failed to connect: Connection refused
06:44:35.593150932 ERROR | [GSTREAMER] Pipeline error: Failed to connect: Connection refused

(wolf:1): GLib-CRITICAL **: 06:44:35.593: g_main_loop_quit: assertion 'g_atomic_int_get (&loop->ref_count) > 0' failed
06:44:35.593266201 ERROR | [GSTREAMER] Pipeline error: Failed to connect: Connection refused

(wolf:1): GLib-CRITICAL **: 06:44:35.593: g_main_loop_quit: assertion 'g_atomic_int_get (&loop->ref_count) > 0' failed
06:44:35.937384923 INFO  | Stopped container: /WolfFirefox_7518890674366070471
06:44:35.960137438 WARN  | [ENET] Received packet from unrecognised client 172.18.0.57:44512

Is there something i'm doing wrong ?

ABeltramo commented 10 months ago

You are right, the error at the end "Failed to connect: Connection refused" is clearly an issue with PulseAudio.
The container will complain about stuff, those error messages in the logs of pulse are absolutely normal and expected; as long as the container is up and running everything should be fine.
There are a couple of things you can check:

solipsist01 commented 8 months ago

So, i finally had some free time :) It looks like the Wolf container starts the wolfpulseaudio container with the wrong environmental variables.

it should be "XDG_RUNTIME_DIR=/tmp/sockets" it seems it makes two serperate vars.

 "Config": {
            "Hostname": "aab6390f2c18",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "4713/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "XDG_RUNTIME_DIR",
                "/tmp/sockets",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "PUID=1000",
                "PGID=1000",
                "UMASK=000",
                "UNAME=root",
                "HOME=/root",
                "TZ=Europe/London"
            ],
            "Cmd": null,
            "Image": "ghcr.io/games-on-whales/pulseaudio:master",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": [
                "/entrypoint.sh"
            ],
            "OnBuild": null,
            "Labels": {
                "org.opencontainers.image.ref.name": "ubuntu",
                "org.opencontainers.image.source": "https://github.com/games-on-whales/gow",
                "org.opencontainers.image.version": "23.04"
            }
        },
ABeltramo commented 8 months ago

Well well, you are absolutely right, we are passing two env variables instead of doing XDG_RUNTIME_DIR=<<runtime_dir>>!
I guess that's working because we still mount /tmp/sockets into /tmp/pulse/ which is the default folder in our custom pulseaudio container.

I still don't see how this is not working for you though:

Do you ever get the line [PULSE] Pulse connection ready in Wolf?

solipsist01 commented 8 months ago

i got pulse working. when wolf starts the pulseaudio container, /tmp/sockets is now mounted into /tmp/pulse inside the container, and it connects! :)

14:43:29.028583076 WARN  | [DOCKER] Container WolfPulseAudio already present, removing first
14:43:29.183985882 DEBUG | 192.168.10.158 [GET] HTTP://192.168.10.253/serverinfo
14:43:29.268542340 DEBUG | 192.168.10.158 [GET] HTTPS://192.168.10.253/serverinfo
14:43:30.720364249 DEBUG | [PULSE] Connecting...
14:43:30.721324866 DEBUG | [PULSE] Pulse connection ready
14:43:32.333061363 DEBUG | 192.168.10.158 [GET] HTTP://192.168.10.253/serverinfo
14:43:32.368541164 DEBUG | 192.168.10.158 [GET] HTTPS://192.168.10.253/serverinfo

i activated the pin, and get presented the apps within moonlight. however, when i launch an application, i get an RTSP handshake error 10054 both when the app is first created, as well as a resume afterwards, when everything exists. i'm on the same network as the server. no firewall rules or anything, and container is running in host networking mode. with GOW / Moonshine i don't had RTSP errors going on :), so i'm pretty sure it's not network related and, i would say rtsp does infact receives data, considering the commands it receives.

What obvious thing am i missing here? :)

14:44:31.033756528 DEBUG | 192.168.10.158 [GET] HTTPS://192.168.10.253/launch
14:44:31.033803995 DEBUG | Setting up input handlers for session: 9490163037892816869
14:44:31.034183430 DEBUG | [INPUT] Created virtual mouse /dev/input/event13
14:44:31.034453845 DEBUG | [INPUT] Created virtual touchpad /dev/input/event14
14:44:31.034680082 DEBUG | [INPUT] Created virtual keyboard /dev/input/event15
14:44:31.034961494 DEBUG | [INPUT] Created virtual controller /dev/input/event16
14:44:31.035425020 DEBUG | [INPUT] Found child: /sys/devices/virtual/input/input74/event16 - /dev/input/event16
14:44:31.035479800 DEBUG | [INPUT] Found child: /sys/devices/virtual/input/input74/js2 - /dev/input/js2
14:44:31.035664900 DEBUG | [INPUT] Created virtual controller /dev/input/event17
14:44:31.036201640 DEBUG | [INPUT] Found child: /sys/devices/virtual/input/input75/event17 - /dev/input/event17
14:44:31.036331072 DEBUG | [INPUT] Found child: /sys/devices/virtual/input/input75/js3 - /dev/input/js3
14:44:31.036861310 DEBUG | [INPUT] Created virtual controller /dev/input/event18
14:44:31.038133171 DEBUG | [INPUT] Found child: /sys/devices/virtual/input/input76/event18 - /dev/input/event18
14:44:31.038287908 DEBUG | [INPUT] Found child: /sys/devices/virtual/input/input76/js4 - /dev/input/js4
14:44:31.038749681 DEBUG | [INPUT] Created virtual controller /dev/input/event19
14:44:31.039627137 DEBUG | [INPUT] Found child: /sys/devices/virtual/input/input77/event19 - /dev/input/event19
14:44:31.039736282 DEBUG | [INPUT] Found child: /sys/devices/virtual/input/input77/js5 - /dev/input/js5
14:44:31.040099877 DEBUG | Host app state folder: /etc/wolf/9490163037892816869/Firefox, creating paths
14:44:31.041504942 DEBUG | [STREAM_SESSION] Create virtual audio sink
14:44:31.041640503 DEBUG | [STREAM_SESSION] Create wayland compositor
14:44:31.041657113 DEBUG | [WAYLAND] Creating wayland display
14:44:31.042231164 DEBUG | [PULSE] Created virtual sink: 3
14:44:31.059581259 DEBUG | 192.168.10.158 [GET] HTTP://192.168.10.253/serverinfo
14:44:31.070998507 DEBUG | [RTSP] received command OPTIONS
14:44:31.083923938 DEBUG | [RTSP] received command DESCRIBE
14:44:31.094075590 DEBUG | WAYLAND_DISPLAY=/tmp/sockets/wayland-1
14:44:31.094362576 DEBUG | [RTSP] received command SETUP
14:44:31.094371289 DEBUG | /proc/driver/nvidia/gpus/0000:00:02.0/information doesn't exists, this might be normal if the GPU is not Nvidia
14:44:31.099828309 DEBUG | /dev/dri/renderD128 vendor: Intel Corporation
14:44:31.100005861 DEBUG | 192.168.10.158 [GET] HTTPS://192.168.10.253/serverinfo
14:44:31.101109911 WARN  | [DOCKER] Container WolfFirefox_9490163037892816869 already present, removing first
14:44:31.107309587 DEBUG | [RTSP] received command SETUP
14:44:31.118038960 DEBUG | [RTSP] received command SETUP
14:44:31.131208213 ERROR | [RTSP] error parsing message
14:44:31.535707154 INFO  | Starting container: /WolfFirefox_9490163037892816869
14:44:31.535754297 DEBUG | Starting container: {
 id: cc41c4e9cebd4438ea77316298feee3dad551918acd0b09098c16f271da1255d
 name: /WolfFirefox_9490163037892816869
 image: ghcr.io/games-on-whales/firefox:edge
 status: 0
 ports: []
 mounts: [/tmp/sockets/pulse-socket:/tmp/sockets/pulse-socket:rw, /tmp/sockets/wayland-1:/tmp/sockets/wayland-1:rw, /etc/wolf/9490163037892816869/Firefox:/home/retro:rw]
 devices: [/dev/input/event13:/dev/input/event13:mrw, /dev/input/event14:/dev/input/event14:mrw, /dev/input/event15:/dev/input/event15:mrw, /dev/input/event16:/dev/input/event16:mrw, /dev/input/js2:/dev/input/js2:mrw, /dev/input/event17:/dev/input/event17:mrw, /dev/input/js3:/dev/input/js3:mrw, /dev/input/event18:/dev/input/event18:mrw, /dev/input/js4:/dev/input/js4:mrw, /dev/input/event19:/dev/input/event19:mrw, /dev/input/js5:/dev/input/js5:mrw, /dev/dri/card0:/dev/dri/card0:mrw, /dev/dri/renderD128:/dev/dri/renderD128:mrw, /dev/dri/card0:/dev/dri/card0:mrw]
 env: ["MOZ_ENABLE_WAYLAND=1", "GOW_REQUIRED_DEVICES=/dev/uinput /dev/input/event* /dev/dri/* /dev/nvidia*", "PULSE_SOURCE=virtual_sink_9490163037892816869.monitor", "GAMESCOPE_REFRESH=60", "PULSE_SINK=virtual_sink_9490163037892816869", "WAYLAND_DISPLAY=wayland-1", "GAMESCOPE_HEIGHT=1080", "PULSE_SERVER=/tmp/sockets/pulse-socket", "XDG_RUNTIME_DIR=/tmp/sockets", "GAMESCOPE_WIDTH=1920", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "PUID=1000", "PGID=1000", "UMASK=000", "UNAME=retro", "HOME=/home/retro", "TZ=Europe/London", "GAMESCOPE_VERSION=3.12.0-beta9", "DEBIAN_FRONTEND=noninteractive", "BUILD_ARCHITECTURE=amd64", "DEB_BUILD_OPTIONS=noddebs"]
}
14:44:34.161185532 DEBUG | 192.168.10.158 [GET] HTTP://192.168.10.253/serverinfo
14:44:34.205892581 DEBUG | 192.168.10.158 [GET] HTTPS://192.168.10.253/serverinfo
14:44:34.234823059 DEBUG | 192.168.10.158 [GET] HTTP://192.168.10.253/serverinfo

This is logs from a 'resume'

14:55:09.269911614 DEBUG | 192.168.10.158 [GET] HTTPS://192.168.10.253/resume
14:55:09.270072508 DEBUG | Host app state folder: /etc/wolf/9490163037892816869/Firefox, creating paths
14:55:09.302177243 DEBUG | [RTSP] received command OPTIONS
14:55:09.313634090 DEBUG | [RTSP] received command DESCRIBE
14:55:09.326071388 DEBUG | [RTSP] received command SETUP
14:55:09.337725550 DEBUG | [RTSP] received command SETUP
14:55:09.346301242 DEBUG | [RTSP] received command SETUP
14:55:09.362838431 ERROR | [RTSP] error parsing message
14:55:11.404459815 DEBUG | 192.168.10.158 [GET] HTTP://192.168.10.253/serverinfo
14:55:11.447443047 DEBUG | 192.168.10.158 [GET] HTTPS://192.168.10.253/serverinfo
14:55:13.271989100 DEBUG | 192.168.10.158 [GET] HTTP://192.168.10.253/serverinfo
14:55:13.323213352 DEBUG | 192.168.10.158 [GET] HTTP://192.168.10.253/serverinfo

This is the actual docker-compose.yml file content:

version: "3.8"
services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    environment:
      - XDG_RUNTIME_DIR=/tmp/sockets
      - HOST_APPS_STATE_FOLDER=/etc/wolf
      - WOLF_LOG_LEVEL=DEBUG
    volumes:
      - /etc/wolf/wolf:/wolf/cfg
      - /tmp/sockets:/tmp/sockets:rw
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /dev/shm:/dev/shm:rw
      - /dev/input:/dev/input:rw
      - /run/udev:/run/udev:rw
    devices:
      - /dev/dri
      - /dev/uinput
    device_cgroup_rules:
      - 'c 13:* rmw'
    network_mode: host
    restart: unless-stopped

docker inspect wolf


 "Config": {
            "Hostname": "debian",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": true,
            "AttachStderr": true,
            "ExposedPorts": {
                "47984/tcp": {},
                "47989/tcp": {},
                "47998/udp": {},
                "47999/udp": {},
                "48000/udp": {},
                "48010/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [

the pulse audio log:

[2023-10-14 14:43:29] Removing all files from /root/.config/pulse
[2023-10-14 14:43:29] Starting pulseaudio
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [pulseaudio] core-util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
W: [pulseaudio] authkey.c: Failed to open cookie file '/root/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key '/root/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to open cookie file '/root/.pulse-cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key '/root/.pulse-cookie': No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
E: [null-sink] util.c: Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
ABeltramo commented 8 months ago

i got pulse working. when wolf starts the pulseaudio container, /tmp/sockets is now mounted into /tmp/pulse inside the container, and it connects!

What have you changed? Are you running the pulse container manually? Wolf should try and set that up automatically when failing to connect to pulseaudio.

when i launch an application, i get an RTSP handshake error 10054

This has been reported by others on Discord but I'm not able to replicate it. Which Moonlight client are you using? Could you please also lower down the WOLF_LOG_LEVEL to TRACE and paste the RTSP messages that Wolf receives?

solipsist01 commented 8 months ago

this morning, i wanted to do a trace now it's working flawlessly i really don't understand why, though, i hate that. if i get it again, i will definately provide the trace.

to get pulse working, i did alot of trial and error. so i'm not 100% sure what hit the spot. i removed all files which are put on several locations. (i was cleaning the config dir only before that) there's files in the config dir, the /tmp/sockets dir, as well as /bin/something. i tried to cleanout everything, and then it worked. perhaps some leftovers from GOW or something, or an old version of a toml i don't know :)

Rikiar73574 commented 5 months ago

just in case, i am facing the same issue and nothing is really working for me.