On Monday 18 May 2009 12:50:50 Paul Davis wrote: > On Mon, May 18, 2009 at 12:34 PM, Fons Adriaensen <[email protected]> wrote: > > Jack-dbus is not just an (optional) server using > > the C API and providing access to it via dbus. > > > > I don not know what exactly is happening but it > > interferes even if clients are just using the > > C API. And it breaks it. > > as far as we can tell, this is true *only* for the auto-start > situation, and that is because of the substantive difference that i > outlined in a previous message about what "auto-start" means in two > different run-time environments. and it showed up for you, as best as > can be determined, because of packaging/build issues that we hope have > been fixed.
So perhaps the problem is that Fons is getting an autostart from somewhere, he knows not where, that he doesn't know how to disable? If there is a simple way to disable jack autostart on his system, can someone clue him in and see if it solves his problems for now? > > everyone involved (i think) agrees that the current way this has to > come to be (a dbus-specific version of libjack) is not the right > solution. we are discussing ways to fix this on #jack at present. all the best, drew _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
