Bug 374511 - Unable to play anything via alsa-lib under user priviledges
Summary: Unable to play anything via alsa-lib under user priviledges
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 8
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-10 11:54 UTC by Jindrich Novy
Modified: 2013-07-02 23:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-26 22:35:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jindrich Novy 2007-11-10 11:54:31 UTC
Description of problem:
When I try to play sound in F8 under ordinary user priviledges I see this:

[AO_ALSA] alsa-lib: confmisc.c:768:(parse_card) cannot find card '0'
[AO_ALSA] alsa-lib: conf.c:3510:(_snd_config_evaluate) function
snd_func_card_driver returned error: No such device
[AO_ALSA] alsa-lib: confmisc.c:392:(snd_func_concat) error evaluating strings
[AO_ALSA] alsa-lib: conf.c:3510:(_snd_config_evaluate) function snd_func_concat
returned error: No such device
[AO_ALSA] alsa-lib: confmisc.c:1251:(snd_func_refer) error evaluating name
[AO_ALSA] alsa-lib: conf.c:3510:(_snd_config_evaluate) function snd_func_refer
returned error: No such device
[AO_ALSA] alsa-lib: conf.c:3982:(snd_config_expand) Evaluate error: No such device
[AO_ALSA] alsa-lib: pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default
[AO_ALSA] Playback open error: No such device
audio_out: alsa9 and alsa1x modules were removed, use -ao alsa instead.


Version-Release number of selected component (if applicable):
alsa-lib-1.0.15-1.fc8.x86_64

How reproducible:
always

Steps to Reproduce:
1. mplayer <any ogg/mp3>
  
Actual results:
audio_out: alsa9 and alsa1x modules were removed, use -ao alsa instead.

Expected results:
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...

Additional info:
Works perfecly under root.

Not a pure F8 installation, but upgraded F7, so that the problem I see may
reveal some configuration issue.

Comment 1 Ra P. 2007-11-21 12:31:41 UTC
Hi,

I had the same problem when upgrading from FC6

The solution I found is to change to ownership of alsa's devices /dev/snd/* to
me (this is how it use to be before the upgrade)

Patch:
--- /etc/udev/rules.d/40-alsa.rules.rpmorig     2007-11-21 12:22:00.000000000 +0200

+++ /etc/udev/rules.d/40-alsa.rules     2007-11-21 12:23:00.000000000 +0200

@@ -1,11 +1,11 @@

 # do not edit this file, it will be overwritten on update

 

-KERNEL=="controlC[0-9]*",      NAME="snd/%k"

-KERNEL=="hwC[D0-9]*",          NAME="snd/%k"

-KERNEL=="pcmC[D0-9cp]*",       NAME="snd/%k"

-KERNEL=="midiC[D0-9]*",                NAME="snd/%k"

-KERNEL=="timer",               NAME="snd/%k"

-KERNEL=="seq",                 NAME="snd/%k"

+KERNEL=="controlC[0-9]*",      NAME="snd/%k",  OWNER="MY-USERNAME"

+KERNEL=="hwC[D0-9]*",          NAME="snd/%k",  OWNER="MY-USERNAME"

+KERNEL=="pcmC[D0-9cp]*",       NAME="snd/%k",  OWNER="MY-USERNAME"

+KERNEL=="midiC[D0-9]*",                NAME="snd/%k",  OWNER="MY-USERNAME"

+KERNEL=="timer",               NAME="snd/%k",  OWNER="MY-USERNAME"

+KERNEL=="seq",                 NAME="snd/%k",  OWNER="MY-USERNAME"

 KERNEL=="mixer0",              SYMLINK+="mixer"

 KERNEL=="dsp0",                        SYMLINK+="dsp"

 KERNEL=="audio0",              SYMLINK+="audio"


Comment 2 Jindrich Novy 2007-11-22 12:07:51 UTC
I actually worked that around by removing pulseaudio, staring ConsoleKit.
Initially I was pretty confused about the sound devices permissions since
owner/group is root/root so no ordinary used has valid permission to use them,
but as soon as ConsoleKit is started it handles the sound device permissions via
ACLs so that it worked after starting ConsoleKit and on.

Comment 3 Martin Stransky 2007-11-26 22:35:19 UTC
ConsoleKit is the right way ;)


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