[Bug]: Steam stuck at "Loading user data"

[cRaZy-bisCuiT]

Describe the Bug

When launching the container, everything works well including the installation of Steam. When launching steam, I'm able to Scan to QR so steam should login. Actually Steam is stuck at "Loading user data".

Steps to Reproduce

1. Follow all commands of the "Docker Compose" tutorial.
2. Login to Steam
3. Steam is stuck at ""Loading user data"

Expected Behavior

Steam should login and allow to use it.

Screenshots

Relevant Settings

---
services:
  steam-headless:
    image: josh5/steam-headless:latest
    restart: unless-stopped
    runtime: ${DOCKER_RUNTIME}
    shm_size: ${SHM_SIZE}
    ipc: host # Could also be set to 'shareable'
    ulimits:
      nofile:
        soft: 1024
        hard: 524288
    cap_add:
      - NET_ADMIN
      - SYS_ADMIN
      - SYS_NICE
    security_opt:
      - seccomp:unconfined
      - apparmor:unconfined

    # NETWORK:
    network_mode: host
    hostname: ${NAME}
    extra_hosts:
      - "${NAME}:127.0.0.1"
    
    # ENVIRONMENT:
    ## Read all config variables from the .env file
    env_file: .env

    # DEVICES:
    devices:
      # Use the host fuse device.
      - /dev/fuse
      # Add the host uinput device.
      - /dev/uinput
      # Add AMD/Intel HW accelerated video encoding/decoding devices (optional)
      - /dev/dri
    # Ensure container access to devices 13:*
    device_cgroup_rules:
      - 'c 13:* rmw'

    # VOLUMES:
    volumes:
      # The location of your home directory.
      - /opt/container-data/steam-headless/home/:/home/default/:rw

      # The location where all games should be installed.
      # This path needs to be set as a library path in Steam after logging in.
      # Otherwise, Steam will store games in the home directory above.
      - /mnt/games/:/mnt/games/:rw

      # The Xorg socket. This will be shared with other containers so they can access the X server.
      # Select only one option or leave commented out to not share the Xorg socket with any other Docker containers.
      #   Option #1) Start a X server in the container to share with any other containers.
      #- /opt/container-data/steam-headless/.X11-unix/:/tmp/.X11-unix/:rw
      #   Option #2) Use an existing X server running on the host.
      #- /tmp/.X11-unix/:/tmp/.X11-unix/:rw

      # Pulse audio socket. This will be shared with other containers so they can access the audio sink.
      # Leave commented out to not share the pulse socket with any other Docker containers.
      #- /opt/container-data/steam-headless/pulse/:/tmp/pulse/:rw


### Version

Build: [2024-02-17 02:36:15] [master] [6cc9f56155f3c7f9fc6bc9c22ef2cbf555029c00] [debian]

### Platform

-  Debian GNU/Linux 12 (bookworm)
- 6.5.13-1-pve unknown unknown GNU/Linux
- Docker version 20.10.24+dfsg1, build 297e128
- docker-compose version 1.29.2, build unknown

### Relevant log output

```Shell
#Everything is started up. Last lines of Docker logs:

[ /etc/cont-init.d/90-configure_vnc.sh: executing... ]
**** Configure VNC ****
Configure VNC service port '32036'
Configure pulseaudio encoded stream port '32037'
Enable VNC server
DONE

[ /etc/cont-init.d/95-setup_wol.sh: executing... ]
**** Configure WoL Manager ****
Disable WoL Manager service.

**** Starting supervisord ****
Logging all root services to '/var/log/supervisor/'
Logging all user services to '/home/default/.cache/log/'

2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/dbus.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/desktop.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/neko.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/pulseaudio.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/steam.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/sunshine.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/udev.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/vnc-audio.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/vnc.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/wol-power-manager.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/xorg.ini" during parsing
2024-02-22 20:48:02,794 INFO Included extra file "/etc/supervisor.d/xvfb.ini" during parsing
2024-02-22 20:48:02,794 INFO Set uid to user 0 succeeded
2024-02-22 20:48:02,797 INFO RPC interface 'supervisor' initialized
2024-02-22 20:48:02,797 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-02-22 20:48:02,797 INFO supervisord started with pid 1
2024-02-22 20:48:03,799 INFO spawned: 'dbus' with pid 243
2024-02-22 20:48:03,801 INFO spawned: 'udev' with pid 244
2024-02-22 20:48:03,802 INFO spawned: 'xorg' with pid 245
2024-02-22 20:48:03,803 INFO spawned: 'audiostream' with pid 246
2024-02-22 20:48:03,804 INFO spawned: 'frontend' with pid 247
2024-02-22 20:48:03,805 INFO spawned: 'pulseaudio' with pid 249
2024-02-22 20:48:03,806 INFO spawned: 'x11vnc' with pid 250
2024-02-22 20:48:03,807 INFO spawned: 'desktop' with pid 251
PULSEAUDIO: Starting pulseaudio service
2024-02-22 20:48:03,829 INFO reaped unknown pid 271 (exit status 0)
2024-02-22 20:48:04,829 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-22 20:48:04,829 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-22 20:48:04,829 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-22 20:48:04,829 INFO success: audiostream entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-22 20:48:04,829 INFO success: frontend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-22 20:48:04,829 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-22 20:48:04,829 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-22 20:48:04,829 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-22 20:48:05,073 INFO reaped unknown pid 319 (exit status 1)

[oldirtdog]

I am having this exact issue with a new install. Just tried to do it on UnRAID 6.11.5 for the first time, and everything seemed fine. Then it just stuck on loading data. I have an AMD GPU and have done any number of suggested tweaks to additional settings and reinstalls.

[alansari]

Could you try adding a variable to the template named STEAM_ARGS and set the value to: -silent -cef-disable-gpu

[cRaZy-bisCuiT]

Well, for me I did find the issue: I had to attach an HDMI cable (or dummy plug which I don't own) to the proxmox host running the docker Container. Otherwise $DISPLAY seems not to be set. Could I work arround that somehow or do I need to do it that way?

@oldirtdog Does that work for you, too?

[oldirtdog]

I hooked up a cable but it didn't change anything. Do you need to have an actual display connected? I can try that later, but I dont have anything at the moment.

EDIT: I did try the STEAM_ARGS thing and that did allow it to launch, but it definitely was not using the GPU (as expected with the flags)

[alansari]

Best performance I've had is indeed with a HDMI dummy plug.
There is a way to get it to run headless if you follow the documentation on lyzardbye's docs using a custom xorg.conf utilizing a trick with twin view
-cef-disable-gpu only Disables GPU usage in Chromium Embedded Framework used by the steam client. Shouldn't effect gaming performance.