ValveSoftware / steam-runtime

A runtime environment for Steam applications
Other
1.17k stars 86 forks source link

No sound, pulseaudio wrapper complains of unrecognised options --start and --log-target=syslog #513

Open amalon opened 2 years ago

amalon commented 2 years ago

No games run through proton have sound with latest proton versions. Primarily using Proton 7.0-3. The proton log and stracing shows that it loads pulsedrv, then tries to run /usr/bin/pulseaudio --start --log-target=syslog. This results in the following output:

pulseaudio: unrecognized option '--start'
pulseaudio: unrecognized option '--log-target=syslog'

then it unloads pulsedrv and falls back to the alsa driver which fails since the device is busy.

It appears to be using ~/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/soldier_platform_0.20220509.0/files/bin/pulseaudio which is a wrapper script which doesn't support --start or --log-target.

On archlinux, tried with steam-runtime and steam-native, no difference.

kisak-valve commented 2 years ago

Hello @amalon, this reads more like an issue with Steam Linux Runtime - Soldier instead of Proton, so I've transferred this issue report to the steam-runtime issue tracker.

RyuzakiKK commented 2 years ago

Can you please provide your system info and the debug logs? You can find the instructions about how to obtain them here https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md#essential-information

Also, what's your audio stack? Are you using PulseAudio in your ArchLinux host system or something else?

amalon commented 2 years ago

Using standard pulseaudio. The only way I can get sound out at the moment from games using proton seems to be with Steam client beta, solder beta, and not opening pavucontrol before the game, but then when I open pavucontrol is just always "Establishing connection to PulseAudio. Please wait..." so I'm guessing its started its own pulseaudio in the container or falling back to alsa that works, but since it doesn't use my simultaneous output configuration (set in paprefs) i only get sound out of the speakers and not my VR headset like I did before.

If I open pavucontrol on desktop before first game launch, sound doesn't work from games using proton. E.g. the below info is opening steam with:

STEAM_LINUX_RUNTIME_LOG=1 steam

and steamvr, then launching lightsaber vr with PROTON_LOG=1, with no sound coming out and the aforementioned errors from pulseaudio wrapper in the proton log.

VERSIONS:

#Name   Version         Runtime Runtime_Version Comment
depot   0.20220602.55                   # Overall version number
pressure-vessel 0.20220601.0
scripts v0.20220527.0-0-g8669533                        # Entry point scripts, etc.
soldier 0.20220601.0    soldier 0.20220601.0    # soldier_platform_0.20220601.0/

slr-app0-t20220625T120405.log:

12:04:05.920730: _v2-entry-point[3954]: argv: /usr/share/steam/compatibilitytools.d/proton-ge-custom/proton run /home/steam/.local/share/Steam/ubuntu12_32/../bin/d3ddriverquery64.exe -d3d12 
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
Fossilize INFO: Overriding serialization path: "/home/steam/.local/share/Steam/shader_cache_temp_dir_d3d12_64/fozpipelinesv6/steamapprun_pipeline_cache".

slr-app477270-t20220625T120532.log:

pid 7533 != 7526, skipping destruction (fork without exec?)
12:05:32.009247: _v2-entry-point[7526]: argv: /home/steam/.local/share/Steam/steamapps/common/Proton\ -\ Experimental/proton waitforexitandrun /home/steam/.local/share/Steam/steamapps/common/LightbladeVR/LightbladeVR.exe 

system information: https://gist.github.com/amalon/0cf33444d7979cf5dd8af15c638b099e

steam-477270.log