[pulseaudio-discuss] jackdbus module, pulse fails to conform on device reservation API

[Ian Malone]

On 4 November 2012 11:23, Ian Malone <ibmalone at gmail.com> wrote:
> Hi,
>
> I'm trying to get a Jack DBUS setup working on Fedora 18. It seems
> pulse refuses to release the audio device when it gets a dbus request
> from jack:
>
> Sat Nov  3 20:08:11 2012: Starting jack server...
> Sat Nov  3 20:08:11 2012: JACK server starting in realtime mode with priority 60
> Sat Nov  3 20:08:11 2012: control device hw:1
> Sat Nov  3 20:08:11 2012: control device hw:1
> Sat Nov  3 20:08:11 2012:  [1m [31mERROR: Failed to acquire device
> name : Audio1 error : Method "RequestRelease" with signature "i" on
> interface "org.freedesktop.ReserveDevice1" doesn't exist
>  [0m
> Sat Nov  3 20:08:11 2012:  [1m [31mERROR: Audio device hw:1 cannot be
> acquired... [0m
> Sat Nov  3 20:08:11 2012:  [1m [31mERROR: Cannot initialize driver [0m
> Sat Nov  3 20:08:11 2012:  [1m [31mERROR: JackServer::Open() failed with -1 [0m
> Sat Nov  3 20:08:11 2012:  [1m [31mERROR: Failed to open server [0m
>
> If pulse is running but doesn't have the device then jack starts okay
> and the sink/source modules get loaded. So this is just a failure in
> negotiating the release.
>
> I'm told this is a problem with pulse's implementation of the
> interface. The only reference I can find is this:
> http://git.0pointer.de/?p=reserve.git;a=blob_plain;f=reserve.txt
>
> Can anyone provide any insight on this issue please?
>

Some further information from one of Fedora's pulse co-maintainers
Brendan Jones:
https://bugzilla.redhat.com/show_bug.cgi?id=872362#c9

> It seems that the module-esound-protocol is loaded be default. It takes a lock
> on the device (see ls /tmp.esd*) which seems to stop it from allowing pusle to
> release the device.

I haven't had time to check this yet, but even if it's true the
message 'Method "RequestRelease" with signature "i" on interface
"org.freedesktop.ReserveDevice1" doesn't exist' seems to suggest that
the dbus interface is not working properly anyway. I've noticed that
it pulse is active but hasn't been used for playback then Jack can
claim the device okay, so possibly this locking issue is only acting
to make that failure to respond to the request visible?

-- 
imalone
http://ibmalone.blogspot.co.uk