[LAD] [Jackit-devel] [PATCH] jack dbus and logs improvement

Krzysztof Foltman wdev at foltman.com
Tue Dec 18 15:12:58 UTC 2007

Nedko Arnaudov wrote:

> So having jackd behave in orthagonal way is not confusing? Like, jackd
> process is running, why my apps cannot connect?!?!?

In normal situations, this jackd process (the launcher) would be only
short-lived (less than a second). It might hang for some reason, because
of faulty driver or something else, but then it would be a rare
exception, not a rule. Plus, it's no worse than what would happen in
non-dbus jack (where jackd would be present in process list, but would
not respond).

If the "jackd in engine mode" (jackd started with --dbus) is running,
applications are able to connect, aren't they?

Or maybe you should describe your "jackd process running, apps can't
connect" scenario in more detail, in case I got it wrong? Basically,
what turn of events results in jackd running but not responding to events?


More information about the Linux-audio-dev mailing list