Bug 704772 - Bugs in alsa-lib prevent the audacious alsa output plugin from working.
Summary: Bugs in alsa-lib prevent the audacious alsa output plugin from working.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: alsa-lib
Version: 6.0
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jaroslav Kysela
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-14 20:06 UTC by Steve Holland
Modified: 2011-12-06 18:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 18:00:08 UTC
Target Upstream Version:

Attachments (Terms of Use)
Patches from mailing list post (2.75 KB, patch)
2011-05-14 20:06 UTC, Steve Holland 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1719 0 normal SHIPPED_LIVE alsa-lib bug fix update 2011-12-06 01:02:14 UTC

Description Steve Holland 2011-05-14 20:06:10 UTC 
Created attachment 498957 [details]
Patches from mailing list post

Description of problem:
Bugs in alsa-lib prevent the audacious alsa output plugin from working. 
For example, on running audacious with the ALSA output plugin selected, you get:  
  ALSA lib pcm.c:221:(snd_pcm_open_noupdate) Unknown PCM default
and no sound is generated

Version-Release number of selected component (if applicable):
alsa-lib-1.0.21-3

How reproducible:
Every time

Steps to Reproduce:
1. Build audacious
2. Try to play through ALSA plugin
3.
  
Actual results:
Error message and no sound

Expected results:
Sound playback

Additional info:

Applying the patches from this page: 
  http://mailman.alsa-project.org/pipermail/alsa-devel/2009-October/022505.html
solves the problem. 

The patches are attached
Comment 5 errata-xmlrpc 2011-12-06 18:00:08 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1719.html
Note You need to log in before you can comment on or make changes to this bug.