[openob-users] Re: A jackd issue as well

Mike, Several of the Jack2 packages are compiled with dbus enabled. This shouldn't be a problem, but on some systems dbus doesn't get started unless you are running X. I've run into this on Ubuntu/Debian systems quite a bit. Jack doesn't actually need X to run, it is possible to compile it without dbus. Sometimes work around this and run jackd2 by doing a dbus-launch to get the dbus daemon started. An alternate is to try Jack1 as you've indicated. Admittedly for a few reasons I often prefer Jack2, but for what you're doing it really doesn't matter which you use. Lorne Tyndale > > G'day along, > > I have installed jackd, but I am getting... > > root@tantive:~# jackd -d alsa -d hw:0 > jackdmp 1.9.11 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2014 Grame. > jackdmp comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > no message buffer overruns > no message buffer overruns > no message buffer overruns > JACK server starting in realtime mode with priority 10 > self-connect-mode is "Don't restrict self connect requests" > Failed to connect to session bus for device reservation Unable to > autolaunch a dbus-daemon without a $DISPLAY for X11 > > Audio device hw:0 cannot be acquired... > Cannot initialize driver > JackServer::Open failed with -1 > Failed to open server > > THere is no X on this box and very little running, I can;t see what or > why it can't get hw:0. > > Any pointers? > > -- > Mike Phillips > Coast FM. > _______________________________________________ > openob-users mailing list -- openob-users(a)lists.talkunafraid.co.uk > To unsubscribe send an email to openob-users-leave(a)lists.talkunafraid.co.uk