On Wed, Jul 19, 2017 at 03:27:25PM -0700, Yuri wrote:
On 07/19/2017 15:08, David Kastrup wrote:
Why and
how does jackd depend on DISPLAY?
One Dbus to rule them all, one Dbus to find
them,
one Dbus to bring them all and on the DISPLAY bind them...
It defines your console.
Only python code depends on DBus in jack1, not C code. The "jackit"
package doesn't depend on DBus.
So I can't figure out how does DBus factor in the jackd boot process.
The situation is different with jack2, which has a --dbus compile
option.
John