systemd fails to start jack

[mobeets]

Below are the logs from sudo journalctl -u looper.service from the last startup:

Dec 12 21:10:33 raspberrypi systemd[1]: Started My service.
jackd: no process found
jackd was not running.
sooperlooper: no process found
sooperlooper was not running.
/home/pi/loop-baby/startup.sh: line 13: jackd_er
SooperLooper 1.7.3
Copyright 2007 Jesse Chappell
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 re
under certain conditions; see the file COPYING f
JACK server starting in non-realtime mode
self-connect-mode is "Don't restrict self connec
audio_reservation_init
Acquire audio card Audio1
creating alsa driver ... hw:1|hw:1|512|3|44100|0
configuring for 44100Hz, period = 512 frames (11
ALSA: final selected sample format for capture: 
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback:
ALSA: use 3 periods for playback
JackTemporaryException : now quits...
Jack main caught signal 2
system:capture_1
system:playback_1
system:playback_2
JackPosixProcessSync::LockedTimedWait error usec
Driver is not running
Cannot create new client
cannot connect to jack
cannot connect to audio driver
cannot initialize sooperlooper
Cannot read socket fd = 3 err = Connection reset
CheckRes error
Could not read result type = 22
Client name = jack_connect conflits with another
Cannot connect to the server
JackShmReadWritePtr1::~JackShmReadWritePtr1 - In
JackShmReadWritePtr::~JackShmReadWritePtr - Init
JACK server not running?
error connecting audio (1)
Released audio card Audio1
audio_reservation_finish
Cannot connect to server socket err = No such fi
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init
JACK server not running?
error connecting audio (2)
Cannot connect to server socket err = No such fi
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init
JACK server not running?
error connecting audio (3)
16:
Connecting USB Midi to Sooperlooper
invalid destination address :0
Setting up Sooper Looper OSC client...
Initializing trellis interface...
Loading empty session from file: /home/pi/loop-b
Set param=input_gain, value=1.0, loop=None
Set param=dry, value=1.0, loop=None
Set param=quantize, value=0, loop=0
Set param=quantize, value=0, loop=1
Set param=quantize, value=0, loop=2
Set param=quantize, value=0, loop=3
Set param=sync_source, value=0, loop=None
Set param=sync, value=0, loop=0
Set param=sync, value=0, loop=1
Set param=sync, value=0, loop=2
Set param=sync, value=0, loop=3
Looper on!

[mobeets]

Recent addition to the looper.service is the line "LimitMEMLOCK=infinity" which helped me get a little bit further. But now the error above is totally vague. "JackTemporaryException : now quits..."? Gee, thanks...

[mobeets]

[Okay, so here I tried running without booting a desktop, and got a new error.]

http://linux-audio.4202.n7.nabble.com/Failed-to-connect-to-session-bus-for-device-reservation-td102866.html

Some things to sort out:

• sudo journalctl -u looper.service doesn't show me the full error. all I know is that it starts with "Failed to connect to session bus for device rese" which is possibly a dbus error
• but I can start it fine manually when running ssh! ssh isn't creating an X server, is it? before I thought this was what I added the export DISPLAY line for.
• do I need to build jack without dbus support?

[mobeets]

[Okay, so here I tried running without booting a desktop, and got a new error.]

Ah. Full error:

Failed to connect to session bus for device reservation /usr/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.