30 Oct
2012
30 Oct
'12
5:42 a.m.
On 10/29/2012 02:12 PM, Patrick Shirkey wrote:
On Tue, October 30, 2012 10:11 am, Len Ovens wrote:
Removing PulseAudio works for me!
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
You got the gist...
On Tue, October 30, 2012 8:35 am, Patrick Shirkey
wrote:
On ubuntu (which normally uses debian src packages), The module name is
module-jackdbus-detect. I don't think I have seen a module called
module-jackdbus-connect even on the pulse site.
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modu…
Hi,
Does anyone know whats going on with pulseaudio-module-jackdbus in
Debian
Wheezy?
On my system the jackdbus module doesn't exist in the repos and the
result
is that pulseaudio doesn't play nice with jack.
I can see that jackd2 was compiled with dbus support so not sure what's
going on with the missing pulse module.
I can see with pacmd list-modules that module-jackdbus-connect is loaded
so the module must be compiled into pulse directly.
So any thoughts on why the module is not kicking in? Even if jackd comes with dbus support, it can be
started without. so use
ps x or similar to check that the running app is jackdbus and not jackd.
There is no jackdbus on debian wheezy, just "jackd" or "jackd2".
If you are using qjackctl there is a checkbox
under misc "Enable D-Bus
interface" that has to be checked.
That helps which means that debian wheezy has support for pulseaudio,
module-jackdbus-detect and jackd2 by default but there is still 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...
====
What I find completely bizarre is that the top 5 hits on google for this
error have people recommending to disable pulseaudio or use an alternate
method to connect. It seems people have known about this issue for a while
and been ignoring it or waiting for someone else to figure it out.