On 01/11/2013 02:37 PM, Brendan Jones wrote: > On 01/11/2013 02:04 PM, David Henningsson wrote: >> This fixes a bug where pulseaudio would give up the device (due to >> a request from JACK), but then immediately grab it again because >> the monitor callback fired, telling that the device is now available. >> >> (Note: the protocol does not specify a timeout, i e if pulseaudio >> is requested to give its device up but JACK does not grab the dbus name, >> at what point is PulseAudio allowed to re-grab it?) >> > > Is this a fix for the bug that is mentioned in this thread? > > http://lists.freedesktop.org/archives/pulseaudio-discuss/2012-November/015254.html Maybe, but it wouldn't surprise me if there was more than one thing that needed fixing here. E g, while debugging, I noticed that if jackd2 first successfully grabbed Audio0 (the dbus name) and then failed on grabbing hw:0 (the alsa device), it seemed like it didn't properly release Audio0 again. There might be more of those things lurking. -- David Henningsson, Canonical Ltd. https://launchpad.net/~diwic
