9 Jul
2017
9 Jul
'17
9:23 a.m.
On Sun, 9 Jul 2017 16:18:50 +0200, Thomas Brand wrote:
On Sun, July 9, 2017 16:15, Ralf Mardorf wrote:
:D
My apologies, I didn't read carefully enough. Without doubts you
mentioned the culprit :).
On Sun, 9 Jul 2017 16:04:10 +0200, Thomas Brand
wrote:
ok :) On Sun, July 9, 2017 13:37, alex wrote:
That's the culprit :). Forget my _wrong_ assumption about something
else grabbing the device.
Failed to connect to session bus for device
reservation Unable to
autolaunch a dbus-daemon without a $DISPLAY$
The following seems to happen: when
you start jackd manually, you
already have a graphical environment providing $DISPLAY which is
again used by dbus. When you start jackd during boot, it will fail
if there is no graphical environment started yet.