[PR #51] [MERGED] Set WOLF_PULSE_CONTAINER_TIMEOUT_MS=30000 to fix missing audio sink (#50) #65

New issue

Closed

opened 2026-10-15 12:55:18 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 12:55:18 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/games-on-whales/unraid-plugin/pull/51
Author: @JBailes
Created: 6/6/2026
Status: ✅ Merged
Merged: 6/6/2026
Merged by: @JBailes

Base: main ← Head: fix/issue-50-pulseaudio-timeout

📝 Commits (1)

990cdd4 Set WOLF_PULSE_CONTAINER_TIMEOUT_MS=30000 so audio survives slow PulseAudio start (#50)

📊 Changes

1 file changed (+2 additions, -0 deletions)

View changed files

📝 scripts/deploy.sh (+2 -0)

📄 Description

Problem

Issue #50: no audio sink in Steam on Unraid (AMD 6750XT).

The D-Bus / cookie warnings in the report are benign (they appear in every Wolf session). The real cause is the WolfPulseAudio startup race.

Wolf starts a sibling WolfPulseAudio container, sleeps a fixed WOLF_PULSE_CONTAINER_TIMEOUT_MS (default 2000ms), then connects to its socket exactly once with no retry (wolf.cpp setup_audio_server). If the connect misses the window Wolf runs with no audio server and apps get no usable sink.

On Unraid the 2s default is fragile: appdata may be on a spun-down or busy disk, and on first launch the pulseaudio:master image may still be pulling. This matches games-on-whales/wolf#374, where raising the timeout to 30s resolved it (confirmed by the Wolf maintainer).

Fix

Set WOLF_PULSE_CONTAINER_TIMEOUT_MS=30000 in both compose templates (write_compose_nvidia and write_compose_standard) in scripts/deploy.sh.

Low risk: it only lengthens a one-time startup wait, and only when Wolf has to start its own PulseAudio container.

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/games-on-whales/unraid-plugin/pull/51 **Author:** [@JBailes](https://github.com/JBailes) **Created:** 6/6/2026 **Status:** ✅ Merged **Merged:** 6/6/2026 **Merged by:** [@JBailes](https://github.com/JBailes) **Base:** `main` ← **Head:** `fix/issue-50-pulseaudio-timeout` --- ### 📝 Commits (1) - [`990cdd4`](https://github.com/games-on-whales/unraid-plugin/commit/990cdd403187d5ccb09c881c716433320450d1cf) Set WOLF_PULSE_CONTAINER_TIMEOUT_MS=30000 so audio survives slow PulseAudio start (#50) ### 📊 Changes **1 file changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `scripts/deploy.sh` (+2 -0) </details> ### 📄 Description ## Problem Issue #50: no audio sink in Steam on Unraid (AMD 6750XT). The D-Bus / cookie warnings in the report are benign (they appear in every Wolf session). The real cause is the WolfPulseAudio startup race. Wolf starts a sibling `WolfPulseAudio` container, sleeps a fixed `WOLF_PULSE_CONTAINER_TIMEOUT_MS` (default **2000ms**), then connects to its socket exactly once with no retry ([`wolf.cpp` `setup_audio_server`](https://github.com/games-on-whales/wolf/blob/stable/src/moonlight-server/wolf.cpp)). If the connect misses the window Wolf runs with no audio server and apps get no usable sink. On Unraid the 2s default is fragile: appdata may be on a spun-down or busy disk, and on first launch the `pulseaudio:master` image may still be pulling. This matches games-on-whales/wolf#374, where raising the timeout to 30s resolved it (confirmed by the Wolf maintainer). ## Fix Set `WOLF_PULSE_CONTAINER_TIMEOUT_MS=30000` in both compose templates (`write_compose_nvidia` and `write_compose_standard`) in `scripts/deploy.sh`. Low risk: it only lengthens a one-time startup wait, and only when Wolf has to start its own PulseAudio container. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 12:55:18 +00:00