[GH-ISSUE #335] How to run pulseaudio - user-session or system-service? #234

New issue

Closed

opened 2026-10-15 12:58:32 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-15 12:58:32 +00:00

Owner

Originally created by @mase76 on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/335

Hi,

I am trying to get Wolf to run on my Debian machine. But it is not clear to me, how I have to run Pulseaudio for Wolf. Must I run it in a user-session with root logged into desktop, or as a system-service? I tried both, but I am not able to connect. It would be nice to know, if I am on the right way. The audio part is not documented very well.

Originally created by @mase76 on GitHub (Jan 12, 2026). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/335 Hi, I am trying to get Wolf to run on my Debian machine. But it is not clear to me, how I have to run Pulseaudio for Wolf. Must I run it in a user-session with root logged into desktop, or as a system-service? I tried both, but I am not able to connect. It would be nice to know, if I am on the right way. The audio part is not documented very well.

bsakaguchi

2026-10-15 12:58:32 +00:00

closed this issue
added the
documentation

question
labels

bsakaguchi commented

2026-10-15 12:58:34 +00:00

Author

Owner

@ABeltramo commented on GitHub (Jan 12, 2026):

Running Wolf outside Docker is definitely not much documented, can I ask you what the goal is?

On my dev machine I just connect to the Pulse socket that's available to my standard user (non-root). You'll have to set permissions accordingly and XDG_RUNTIME_DIR IIRC. Wolf will first do an attempt at connecting to Pulse and, if that fails, it'll fallback to spinning up a Docker container. If you are still going to let Wolf use a Docker socket you can use the fallback and just let it spin our Pulse-in-a-container which should work..

@ABeltramo commented on GitHub (Jan 12, 2026): Running Wolf outside Docker is definitely not much documented, can I ask you what the goal is? ---- On my dev machine I just connect to the Pulse socket that's available to my standard user (non-root). You'll have to set permissions accordingly and `XDG_RUNTIME_DIR` IIRC. Wolf will first do an attempt at connecting to Pulse and, if that fails, it'll fallback to spinning up a Docker container. If you are still going to let Wolf use a Docker socket you can use the fallback and just let it spin our Pulse-in-a-container which should work..

bsakaguchi commented

2026-10-15 12:58:34 +00:00

Author

Owner

@mase76 commented on GitHub (Jan 14, 2026):

The fallback method works. I run Wolf on a headless server. I had several problems, because I wanted to test everything with an old machine and a GTX750. That did not work. Now I use a RTX3060 and it runs.

@mase76 commented on GitHub (Jan 14, 2026): The fallback method works. I run Wolf on a headless server. I had several problems, because I wanted to test everything with an old machine and a GTX750. That did not work. Now I use a RTX3060 and it runs.