Mikel Astiz 1db09d3013 reserve: Fix leaking NameLost signals after release+acquire ... The use of the pseudo-blocking D-Bus calls leads to the problem that NameLost signals are received after the reply to ReleaseName(). The problem with this is that a later acquisition of the same audio device can potentially receive the NameLost signal corresponding to the previous instance, due to the fact that the signal hasn't been popped from the D-Bus message queue. The simplest approach to solve this problem is to poll the actual name owner from the D-Bus daemon, in order to make sure that we did really lose the name. The proposal uses a blocking call to GetNameOwner to avoid incosistent states in the internal APIs: it would otherwise be possible to have a "busy" device before the reservation has been lost, in the unlikely case if some other process acquires the name before we got the confirmation that the NameLost was actually true.		2013-02-18 19:35:28 +02:00
..
daemon	conf: Load bluetooth-policy module by default	2012-11-29 05:39:30 +02:00
modules	reserve: Fix leaking NameLost signals after release+acquire	2013-02-18 19:35:28 +02:00
pulse	mainloop: Don't care about the mainloop state variable when waking up the mainloop.	2012-11-15 17:57:51 +02:00
pulsecore	core: Remove bad free() call	2012-11-19 21:32:18 +05:30
tests	Revert "tests: modify alsa-time-test to use 'check' framework"	2012-11-05 17:48:20 +05:30
utils	pacat: Replace read(), write() with pa_* equivalent.	2012-10-23 12:12:37 +05:30
.gitignore	.gitignore: Add cpu-test.	2012-09-07 17:22:10 +03:00
depmod.py	remove remaining $	2008-06-18 22:38:32 +02:00
Makefile.am	Revert "tests: modify alsa-time-test to use 'check' framework"	2012-11-05 17:48:20 +05:30
map-file	introspect: Add functions to handle the latency offset.	2012-06-30 14:41:08 +03:00