Ardour crashes when trying to start jackd

**Describe the bug**

Ardour crashes when trying to start jackd as part of its startup sequence.

**To Reproduce**
Steps to reproduce the behavior:
1. `sudo pkg -y install ardour6`
2. On the command line, start `ardour6` (so that you can see the error messages on the command line)
3. Without touching anything else, click on "Start" next to the red "Stopped"


**Expected behavior**
Works

**Screenshots**

```
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JACK command line will be: /usr/local/bin/jackd -t 200 -p 2048 -R -T -d oss -n 2 -r 44100 -p 1024
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot lock down 107341338 byte memory area (Cannot allocate memory)
zsh: segmentation fault ardour6
```

Manually tring to run:

```
FreeBSD% /usr/local/bin/jackd -t 200 -p 2048 -R -T -d oss -n 2 -r 44100 -p 1024
jackdmp 1.9.16
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2020 Filipe Coelho.
jackdmp 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
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Cannot lock down 107341338 byte memory area (Cannot allocate memory)
JackOSSDriver::OpenInput failed to open device : ../freebsd/oss/JackOSSDriver.cpp@637, errno = 45
JackTemporaryException : now quits...
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
```

Why does this JACK thing _never_ "just work"? My experience with it so far has been the exact opposite of "plug and play" whenever I had to interact with it, usually resulting in frustration. Can we get it to "just work" (without the user needing to fiddle around with it) on helloSystem?

**Version (please complete the following information):**
- Live ISO or installed system to disk: Installed
- FreeBSD version: 13.0-RELEASE
- helloSystem build: 0.7.0 (Build 0G126)
- Running in a virtual machine: no