[alsa-devel] [Fwd: Re: [pulseaudio-discuss] pulseaudio debug mode]
superquad.vortex2 at gmail.com
Mon Jul 26 15:20:58 CEST 2010
2010/7/26 Colin Guthrie <gmane at colin.guthr.ie>
> 'Twas brillig, and Raymond Yau at 26/07/10 04:22 did gyre and gimble:
> > But I have another question ,
> > did update manager stop pulseaudio server when the update manager want to
> > update pulseaudio package ?
> > Actually I don't notice yum -y update stop the PA server if it updated
> > pulseaudio package (install new pulseaudio and remove old pulseaudio
> > package) and restart PA server on Fedora 10
> PA is *not* restarted when a new version is installed and I suspect this
> does not happen on Fedora either (but I could be wrong).
> The reason is that PA is a per-user daemon, not a system service. If
> three users were logged in, then each of their PA servers would need to
> be killed and restarted but due to console-kit, only the active user
> would get access to the devices which could cause enumeration issues etc.
> It could maybe be handled better, but doing so would be rather complex.
Yes , I know that PA is not a system service
how do you setup PA for three users logged in with each of their PA server
running even when you have three sound cards since you will need to hack the
udev rule to exclude the other two sound cards ?
I got "Too many inputs per sink" error on PA server during software
install/remove on last week when I run pulseaudio on a terminal.
No much info in the server log, the most common PA clients were "tooltips
popup" when I move the mouse cursor across the different part/icon on the
Is there any limit on the the number of PA clients connected to PA server ?
More information about the Alsa-devel