Unit jack.service not found

Patchbox OS
1

Hello,

Today I did a fresh install of the 2024-04-04 image. I am using the patchbox config utility to try to start Jack with device hw:CODEC (my USB audio interface), but it is giving me the following each time:

Failed to restart jack.service: Unit jack.service not found.
Jack service restarted!
Waiting for Jack to boot...
Error: Failed to start Jack service! Try different settings!

For the software I’m trying to use (written in Python using the pyo library), I had to run: sudo apt-get install libjack-dev libsndfile1 libsndfile1-dev

and I wonder if libjack-dev is messing with Jack here. A couple of days ago on a completely fresh install of Patchbox, same beta version, it worked interacting with hw:CODEC. I have tried rebooting.

Following a previous question, here is the output of sudo journalctl -u jack.service:

Nov 26 03:06:41 patchbox systemd[1]: jack.service: Scheduled restart job, restart counter is at 4.
Nov 26 03:06:41 patchbox systemd[1]: Stopped jack.service - JACK Server.
Nov 26 03:06:41 patchbox systemd[1]: Started jack.service - JACK Server.
Nov 26 03:06:41 patchbox jackdrc[987]: Failed to create secure directory (/nonexistent/.config/pulse): No such file or directory
Nov 26 03:06:41 patchbox jackdrc[987]: jackdmp 1.9.21
Nov 26 03:06:41 patchbox jackdrc[987]: Copyright 2001-2005 Paul Davis and others.
Nov 26 03:06:41 patchbox jackdrc[987]: Copyright 2004-2016 Grame.
Nov 26 03:06:41 patchbox jackdrc[987]: Copyright 2016-2022 Filipe Coelho.
Nov 26 03:06:41 patchbox jackdrc[987]: jackdmp comes with ABSOLUTELY NO WARRANTY
Nov 26 03:06:41 patchbox jackdrc[987]: This is free software, and you are welcome to redistribute it
Nov 26 03:06:41 patchbox jackdrc[987]: under certain conditions; see the file COPYING for details
Nov 26 03:06:41 patchbox jackdrc[987]: JACK server starting in realtime mode with priority 95
Nov 26 03:06:41 patchbox jackdrc[987]: self-connect-mode is "Don't restrict self connect requests"
Nov 26 03:06:41 patchbox jackdrc[987]: creating alsa driver ... hw:vc4hdmi0|hw:vc4hdmi0|128|2|44100|0|0|nomon|swmeter|soft-mode|16bit
Nov 26 03:06:41 patchbox jackdrc[987]: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Nov 26 03:06:41 patchbox jackdrc[987]: Cannot initialize driver
Nov 26 03:06:41 patchbox jackdrc[987]: JackServer::Open failed with -1
Nov 26 03:06:41 patchbox jackdrc[987]: Failed to open server
Nov 26 03:06:41 patchbox systemd[1]: jack.service: Main process exited, code=exited, status=255/EXCEPTION
Nov 26 03:06:41 patchbox systemd[1]: jack.service: Failed with result 'exit-code'.

Many thanks,
Paul

2

Make sure blokas-jack package is installed. Sometimes installing some package can end up uninstalling some other packages, before confirming, look at the list it provides on changes it will do and check for anything unexpected.

3

Thank you so much. It had indeed been uninstalled. I installed blokas-jack and after a reboot I now have jack with pyo connecting.

(More specifically I installed libjack-jackd2-dev, which removed libjack-dev (I didn’t realize jack2 is preferred), and then installed blokas-jack, which caused no further changes. This extra info is in case any pyo users are finding this. I’m adding documentation soon on what led to a successful pyo install soon over on my Github.)

1 Like