'Twas brillig, and Noel David Torres Ta?o at 14/12/10 17:53 did gyre and gimble: > (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 Hmm, interesting. pulseaudio --start should basically exit when a system-wide instance is present IIRC. I'll dig through the code and do some experiments to try and work out what's going on. As I don't use system wide myself, I'm maybe missing something. I'll try and get back to you soon. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
