Bug 458611

Summary:	Pulseaudio permissions not correct by default
Product:	[Fedora] Fedora	Reporter:	Russell Miller <rmiller>
Component:	pulseaudio	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	lkundrak, pierre-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-08-11 17:52:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Russell Miller 2008-08-10 21:47:56 UTC

Description of problem:

udevd doesn't create the alsa devices owned by pulse-rt... so pulseaudio can't open them.  Thus, pulseaudio doesn't work.  The user also needs to be added to pulse-rt, and is not.  I don't know how to improve that, perhaps have anyone who starts pulseaudio automatically get added to the group?

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

0.9.10

How reproducible:

Well, it was a problem for me..

Steps to Reproduce:
1. Install fedora
2. Start KDE
3. Try to play a sound
  
Actual results:


Expected results:


Additional info:

I fixed it by adding a 00-permissions.rules to udev.d which created the devices with the correct group ownership.

Comment 1 Lennart Poettering 2008-08-11 17:52:08 UTC

Uh?

pulse-rt is a group for allowing individual users run their PA instances with real-time scheduling (hence pulse-'rt'). It is completely unrelated to device access permissions.

PA is run as user instance. Thus the user you are running PA as needs access to the audio device. By default the user that is logged in on the active console gets access to the audio device files. This is managed via ConsoleKit/HAL.

Comment 2 Russell Miller 2008-08-11 18:29:23 UTC

The fact of the matter is that by default I started the window manager from the open console that I had logged into and pulseaudio *didn't work* until I changed the ownership of the audio files.  Therefore, I am going to have to respectfully insist that this is a bug - if you start KDE and audio doesn't work out of the box, it's a bug.

Now what's *causing* the bug may be a different story and I may have missed something underlying.  It's altogether possible.

You stated yourself:

"PA is run as user instance. Thus the user you are running PA as needs access to
the audio device. By default the user that is logged in on the active console
gets access to the audio device files. This is managed via ConsoleKit/HAL."

The user that was logged in on the active console did not have access to the audio device files.  I did not get sound to working until I added the rules to ensure that the audio files were accessible by the logged in user, therefore, something's not working right.

--Russell