[pulseaudio-tickets] [PulseAudio] #773: Autospawn fails for second user on a given system if the first user is already running PA.

[PulseAudio]

#773: Autospawn fails for second user on a given system if the first user is
already running PA.
---------------------+------------------------------------------------------
  Reporter:  coling  |       Owner:  lennart
      Type:  defect  |      Status:  new    
 Milestone:  0.9.22  |   Component:  daemon 
Resolution:          |    Keywords:         
---------------------+------------------------------------------------------

Comment(by coling):

 Just going on observations - about to dive into the code.

  1. User A logs into X. Start's pulseaudio via one mechanism or another
 (in this test case due to auto-respawning from libcanberra, I have User A
 set to *not* autospawn via their own ~/.pulse/client.conf - global is as
 per default (i.e. autospawning is enabled). At X login PA is started via
 XDG.
  2. User B logs into tty1. paplay /some/sound.wav: Connection Refused.
  3. Go back to User A, pulseaudio -k (ensure no instance is running).
  4. Go back to User B on tty1 and repeat last command: Works and PA is
 autospawned for that user.

 Double confirm:
  5. Still as User B, pulseaudio -k.
  6. Go back to User A, start-pulseaudio-x11
  7. Go back to User B, repeat paplay. Connection Refused again..

 So (from observation) something in the autospawning code prevents User B
 from starting PA when User A has already done so.

 There is no system wide config on this system and User B is a fresh user
 account.

-- 
Ticket URL: <http://pulseaudio.org/ticket/773#comment:2>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server