yes, when i run it manually it’s fine/ source ~/.jackdrc ..will start jackd with the correct configuration. unfortunately, if i than start my client, it will complain the hardware is already in use…

I don’t believe i have. Thats jack 2 isn;t it?

yes, I remember specifically having to use jack1 because i’m not running any graphical environment and thus d-bus was missing. I don’t mind either way, I’m just trying to set up a kind of minimal viable system. fokke

ok did get a little bit further: i’ve changed my jackdrc to: /usr/bin/jackd --realtime -p1024 -dalsa -r48000 -p64 -n2 -D -Chw:MADIFXtest -Phw:MADIFXtest previously I also had a commented out line there, don’t know if it made a difference, but anyway. Now jackd seems to start with the right config, but i’m getting an error: connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file or directory) jackd 0.125.0rc1 Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns JACK compiled with System V SHM support. loading driver .. apparent rate = 48000 creating alsa driver ... hw:MADIFXtest|hw:MADIFXtest|64|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit float little-endian ALSA: use 128 periods for capture ALSA: final selected sample format for playback: 32bit float little-endian ALSA: use 128 periods for playback and then : **starting device...jack main caught signal 12 looks like its trying to read shared memory but it can’t for some reason? Any knows why this could happen? cheers, Fokke

ok, thanks. I’m assuming the jackd is disconnecting because of the shared memory isssue? connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file or directory) it looks like /dev/shm/jack_0 is briefly created when the client starts, but not /dev/shm/jack-0/default/jack_0

On Thu, Aug 02, 2018 at 09:44:00PM +0200, Fokke de Jong wrote: I'm glad you got jackd going. Even a sentence explaining the solution you found is a nice way to give back to the community that assists you. In general, as you learn more about linux, you will find that you rarely have to reboot your system when making changes. I believe it's now possible to install a new kernel on a running system. Installing/removing drivers (e.g. kernel modules) is also something possible without rebooting. Unlike, for example windows, that has to reboot after every patchset when reinstalling from instal media. I do find that X or X apps can hang from time to time, so setting up X to terminate on Ctrl-Alt-Backspace so you can restart X is quite helpful. I use a terminal multiplexer, which comes back with all my terminals, so that part is pretty convenient. Good luck with JACK. I think most users find problems are rare once you get it set up properly due to the well-though-out design excellent work by the maintainers. -- Joel Roth

On Fri, 3 Aug 2018 09:49:15 +0200, Fokke de Jong wrote: The '/usr/lib/x86_64-linux-gnu/libjack*so' symlinks against '/usr/lib/x86_64-linux-gnu/libjack*so*', as well as the header files provided by https://packages.ubuntu.com/artful/amd64/libjack-jackd2-dev/filelist (jack2) are required to build apps, they are not required at runtime. The additional *.a files provided by https://packages.ubuntu.com/artful/amd64/libjack-dev/filelist (jack1) are also not required at runtime. Without the 'dev'elopment packages you can't build apps that should use jack. Once you build such apps, you could remove those packages. That Debian and Ubuntu split jack packages https://tracker.debian.org/pkg/jackd2 https://tracker.debian.org/pkg/jack-audio-connection-kit and that to workaround the jack1/jack2 'issue' the virtual 'jack' package is required, not necessarily could be considered a 'user-friendly' policy and package management. Arch Linux has got a different policy and another package management. Even a clueless Arch Linux user could _not_ come in the position to wonder, if a jack package might be missing, since jack1, as well as jack2 are each provided by a single package and no virtual package is required either. IIRC in the past there indeed were symlink issues, since the Debian and/or Ubuntu maintainers didn't split the packages correctly.