Bug 555112 - openal-soft default configuration seemingly results in buggy behaviour / crashes
Summary: openal-soft default configuration seemingly results in buggy behaviour / crashes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openal-soft
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Thomas Kowaliczek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-13 17:47 UTC by Mark Williamson
Modified: 2010-01-19 19:34 UTC (History)
4 users (show)

Fixed In Version: 1.10.622-7.931f5875cdc4ce0ac61a5110f11e962426e53d99git.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-14 22:25:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mark Williamson 2010-01-13 17:47:55 UTC
Description of problem:

When using default configuration I currently find that warzone2100 crashes at startup, although  I believe it has worked for me in the recent past under Fedora 12 on the same system.

A self-compiled version of Black Shades Elite (http://home.gna.org/blackshadeselite/) exhibited crackles and pops in audio playback with the default configuration, plus trouble closing the audio device connection at exit, which prompted me to investigate the interaction of OpenAL and PulseAudio.

This page suggested that OpenAL now supports PulseAudio directly:
http://wiki.archlinux.org/index.php/PulseAudio#Configuration_of_OpenAL_for_PulseAudio
so I changed my ~/.alsoftrc to include the line "drivers = pulse".  This resolved both the crash of Fedora's WarZone 2100 and the audio problems with my Black Shades Elite.

I am not sure whether the underlying bug here is in PulseAudio, in PulseAudio's ALSA emulation, in OpenAL or in WarZone 2100.  But I do wonder if OpenAL might be able to use PulseAudio by default in future?

Version-Release number of selected component (if applicable):

Version    : 1.10.622                                                                                                                                                            
Release    : 6.0ceaa01c3de75c946ff2e7591e7f69b28ec00409git.fc12                                                                                                                  

How reproducible:

Every time WarZone 2100 is started with default configuration.

Steps to Reproduce:
1. Install WarZone 2100 with fresh Fedora 12 install.
2. Run it - segmentation fault on startup.
  
Actual results:

Crash.

Expected results:

Successful startup with audio.

Additional info:

I have the RPM Fusion free repository and the adobe-linux-i386 repositories enabled on this system.  I am using the KDE desktop.  System was installed from the x86_64 Live KDE spin.

Comment 1 Thomas Kowaliczek 2010-01-13 22:09:00 UTC
Upstream have fix that with pulseaudio in the .alsoftrc.
I will pusg an new version of it on the next days. But i don´t know whether it will fix the warzone problem.

Comment 2 Fedora Update System 2010-01-13 22:48:02 UTC
openal-soft-1.10.622-7.931f5875cdc4ce0ac61a5110f11e962426e53d99git.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/openal-soft-1.10.622-7.931f5875cdc4ce0ac61a5110f11e962426e53d99git.fc12

Comment 3 Thomas Kowaliczek 2010-01-13 22:48:59 UTC
Please test it with this version :)

Comment 4 Mark Williamson 2010-01-14 01:38:37 UTC
(In reply to comment #3)
> Please test it with this version :)    

Hi Thomas,

I installed the updates and removed my ~/.alsoftrc.  Warzone2100 now doesn't crash and audio is glitch-free with Black Shades Elite, so I guess the update has done the trick - thanks for the quick response :-)

Cheers,
Mark

Comment 5 Thomas Kowaliczek 2010-01-14 22:25:03 UTC
No problem and thank you for testing :)

Comment 6 Fedora Update System 2010-01-19 19:34:54 UTC
openal-soft-1.10.622-7.931f5875cdc4ce0ac61a5110f11e962426e53d99git.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.