Bug 1189681

Summary: No sound in xonotic-sdl after update to libSDL 2.0.16
Product: [openSUSE] openSUSE Tumbleweed Reporter: Grósz Dániel <groszdanireg>
Component: OtherAssignee: Jan Engelhardt <jengelh>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: pujos.michael
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Grósz Dániel 2021-08-21 02:39:59 UTC
After updating Tumbleweed to 20210817, containing libSDL2-2_0-0 2.0.16-1.1, there is no sound in the game Xonotic when started with the xonotic-sdl command. Xonotic doesn't even show up as a Pulseaudio client application at all. (I use KDE Plasma on X.org. The xonotic version is 0.8.2-6.1, not changed recently.)

When starting Xonotic with the xonotic-glx command, sound works. (There are a few differences between using the sdl and the glx version, such as mouse acceleration.) I don't know if there are other SDL applications affected; I've tried notpacman (a game that uses the Löve (love) engine, which depends on libSDL2-2.0.so.0()(64bit)) and it has sound.

If I downgrade to libSDL2-2_0-0 2 2.0.14-1.8, from Tumbleweed 20210810, xonotic-sdl has sound again.
Comment 1 Michael Pujos 2021-08-24 14:53:40 UTC
This has been reported on the mailing0list with a workaround:


On Monday 2021-08-23 21:09, Len Nordstrom wrote (via private):
>
> The most recent version of SDL no longer seems to seems to be communicating with Pulse Audio.
> After updating to SDL 2.0.16 all my games that use SDL2 lost all sound.

SDL2 does strict checking of the module name, something it only did 
*very* loosely previously (commit 
25f9ed87ff6947d9576fc9d79dee0784e638ac58).

The problem is in the pulseaudio RPM which:

/etc/profile.d/pulseaudio.sh:export SDL_AUDIODRIVER=pulse
/etc/profile.d/pulseaudio.csh:setenv SDL_AUDIODRIVER pulse

A cursory play-around-a-bit tells me this should be 
"pulseaudio", not "pulse".
Comment 2 Jan Engelhardt 2021-08-27 12:07:31 UTC
Fix is already pending.

*** This bug has been marked as a duplicate of bug 1189778 ***