[pulseaudio-discuss] strange pulse / jack behaviour

Tanu Kaskinen tanuk at iki.fi
Wed Oct 31 10:29:25 PDT 2012


On Thu, 2012-11-01 at 03:58 +1100, Patrick Shirkey wrote:
> > On Thu, 1 Nov 2012 03:08:09 +1100
> > Patrick Shirkey <pshirkey at boosthardware.com> wrote:
> >> 3: The current situation is that I cannot run jackd (jack2 -1.9.9) with
> >> "dbus enabled" in qjackctl misc settings window because I get an error :
> >>
> >> ++++
> >> Failed to acquire device name : Audio0 error : Method "RequestRelease"
> >> with signature "i" on interface "org.freedesktop.ReserveDevice1" doesn't
> >> exist
> >> Audio device hw:0 cannot be acquired..
> >> ++++

For some reason pulseaudio isn't handling the dbus messages. You could
attach "pulseaudio -vvv" output, maybe the log contains something
related error messages.

> module-jackdbus-detect is supposed to release the lock on the device when
> jackdbus (jackd2) starts and then auto reconfigure and connect to
> jackdbus/jackd2 loading the jack-sink/source modules once jackdbus/jackd2
> has successfully started.

FYI, actually module-jackdbus-detect isn't involved with the device
releasing. That part is implemented directly in the alsa modules. For
some reason pulseaudio isn't handling the dbus messages, you could
attach "pulseaudio -vvv" output, maybe the log contains something
related error messages. 

-- 
Tanu



More information about the pulseaudio-discuss mailing list