[PATCH] reserve-monitor: Don't trigger on our own events

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2013-01-11 at 14:39 +0000, Ian Malone wrote:
> On 11 January 2013 13:37, Brendan Jones <brendan.jones.it at gmail.com> 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?)
> >>
> 
> Thank you!
> 
> >
> > Is this a fix for the bug that is mentioned in this thread?
> >
> > http://lists.freedesktop.org/archives/pulseaudio-discuss/2012-November/015254.html
> >
> 
> Looks like it, I'll try to find some time to test at the weekend.

As I mentioned in the other mail, this looks equivalent to the patch
that I sent earlier. That patch didn't solve the bug where pulseaudio
would own the bus name, but not implement the interface for requesting
device release.

-- 
Tanu



[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux