[pulseaudio-discuss] Pulseaudio for two sessions at the same time

Noel David Torres Taño envite at rolamasao.org
Tue Dec 14 09:53:31 PST 2010


On Martes 14 Diciembre 2010 17:20:37 Colin Guthrie escribió:
> 'Twas brillig, and Noel David Torres Taño at 14/12/10 16:41 did gyre and
> 
> gimble:
> > On Martes 14 Diciembre 2010 12:22:17 Michał Sawicz escribió:
> >> Dnia 2010-12-14, wto o godzinie 12:11 +0000, Noel David Torres Taño
> >> 
> >> pisze:
> >>> Yes, thanks, but... How to do it? Is it just to set a system-wide
> >>> server or is
> >>> there something to do in its config and/or in both $HOMEs and/or UNIX
> >>> groups?
> >> 
> >> See http://www.pulseaudio.org/wiki/SystemWideInstance
> >> 
> >> First google hit for 'pulseaudio system wide'
> > 
> > That does NOT answer my question about audio group access, config on the
> > $HOMEs and the like. Thanks, but I learned to read when I was quite
> > young.
> 
> No need to be rude to people who post helpful links.

True, my fault (even when not helpful for me).
> 
> > That page only says that both users should be on pulse-access group, but
> > does not say if, for example, .pulse-cookie must be the same, or if
> > .pulse/client.conf has to be tweaked.
> 
> It also doesn't say how much RAM you need nor whether it works if the
> day has the letter 'T' in it... because they are not relevant :p
> 
> The fact you know about these additional parts of PA is actually working
> against you here - you know too much and it means you try to push them
> into a situation where they are not mentioned because they are not
> important!
> 
> But cheekyness aside, the cookie is not used in system wide mode, the
> access is controlled via the membership of the pulse-access group.

Ok. Tried but... (continues below)
> 
> There should be no tweaks needed on .pulse/client.conf (the file should
> not even exist unless something manual has been done).

Ok too
> 
> HTHs
> 
> Col

(continues here) I've deleted .pulse and .pulse-cookie to be sure, removed 
both accounts from audio group and set them both in pulse-access group. Still 
first session opened gets sound (even when changing sessions, so ConsoleKit is 
not in the way) and secondly opened one gets no sound. May it be that extra PA 
processes are opened? How to avoid that and get each session connect to the 
system-wide PA?

$ ps -A u | grep pulse
pulse    12594  0.0  0.1 273444  5132 ?        S<sl 16:52   0:01 
/usr/bin/pulseaudio --system --daemonize --high-priority --log-target=syslog 
--disallow-module-loading=1
user1    15671  0.0  0.1 218140  5144 ?        Ssl  17:41   0:00 
/usr/bin/pulseaudio --start
user2    16193  0.4  0.0 335412  3868 ?        Ssl  17:45   0:00 
/usr/bin/pulseaudio --start
user1   16306  0.0  0.0   9612   892 pts/1    S+   17:46   0:00 grep pulse

Thanks

Noel
er Envite



More information about the pulseaudio-discuss mailing list