Ardour8 still chasing "find a trout" in Debian12 - logging? stereo channels? unattended install?

Installation & Configuration Linux
#1

A few questions as I pursue the elusive Trout.

First, the news. I love the installer for the official-releases – never tried that before.

Now, the puzzler. My understanding of the failure is maturing. On Deb 12 it seems that it will run perfectly… once. On subsequent running, it can’t start Jack and after the usual four attempts it terminates with my Favorite Error Message Ever and specifies “audio-midi engine setup failed.”

This happens with Ardour7 (installed with apt) and Ardour8 (official-release installer). In both cases they run fine if Jack (installed with apt) is already running.

I have the feeling there’s more-detailed logging available – but I can’t figure out where it is.

Thanks in advance.

PS: Ardour8 - when I add Audio tracks (specifying anything less than 5 channels) I get 5-in/5-out tracks.

PS: Is there an “unattended” mode for the script that I can stick in a shell script that preloads Ardour on a server? I was hoping “quiet” would do that, but it still asks for responses.

PS: Is there a way to load a specific-version official-release?

#2

“Preloads”? Not sure what that means.

You can start Ardour specifying a session name and a template, something like:

/opt/Ardour-8.0.0/bin/ardour8 -N $(date +%Y%m%d\.%H%M) -T MyExistingTemplate

Where I create my session with the current datetime as the name, as I want to start it quickly to record a new idea.

$ /opt/Ardour-8.0.0/bin/ardour8 --help
Usage: Ardour [ OPTIONS ] [ SESSION-NAME ]

Ardour is a multichannel hard disk recorder (HDR) and digital audio workstation (DAW).

Options:
  -a, --no-announcements      Do not contact website for announcements
  -A, --actions               Print all possible menu action names
  -b, --bindings              Display all current key bindings
  -B, --bypass-plugins        Bypass all plugins in an existing session
  -c, --name <name>           Use a specific backend client name, default is ardour
  -d, --disable-plugins       Disable all plugins (safe mode)
  -h, --help                  Print this message
  -k, --keybindings <file>    Path to the key bindings file to load
  -m, --menus file            Use "file" to define menus
  -n, --no-splash             Do not show splash screen
  -N, --new <session-name>    Create a new session from the command line
  -O, --no-hw-optimizations   Disable h/w specific optimizations
  -P, --no-connect-ports      Do not connect any ports at startup
  -S, --sync                  Draw the GUI synchronously
  -T, --template <name>       Use given template for new session
  -v, --version               Print version and exit


Report bugs to http://tracker.ardour.org
Website http://ardour.org
#3

ahem… that was not my best-worded sentence ever. here’s a better one:

PS: Is there an “unattended” mode for the official-version installer script that I can stick in my shell script that preloads Ardour on a bare-metal Debian12 server? I was hoping “quiet” would do that, but it still asks for responses.

but… even that isn’t going to work, because i can’t download the installer-script with curl, so that whole idea isn’t going to work. chalk that one up to “never mind.”

#4

Yeah, I don’t understand what you really want. Bare-metal? As opposed to a virtual machine? What does that have to do with anything? I can’t comprehend why you’re throwing all this jargon out there. Just trying to help. I’m sure curl should be able to download the installer, but it may require a little scripting around it to navigate the authentication.

Are you basically asking how to install and run Ardour in a GUI-less environment?

And the “preloading” clarification did not help at all :slight_smile:

#5

Do you mean install Ardour?

The default installer requires interaction, but if you are tech-savvy you can probably manually deploy it.

See Ardour-8.0.0-x86_64.run --help then do something like

sh Ardour-8.0.0-x86_64.run --noexec --keep --target /tmp/Ardour/
ls -a /tmp/Ardour
cd /opt
sudo tar xf /tmp/Ardour/Ardour_x86_64-8.0.0.tar

This does not create a .desktop menu item, icons, nor create symlink to put Ardour8 in $PATH etc. read the install scripts in /tmp/Ardour/.

#6

egad - my double-super badly written sentence. sorry folks!

what i’ve been doing for a while now is installing Ardour on virtual Debian 11 servers using apt inside a shell-script on a Linode (brand of virtual server). “bare metal” is just an old-guy way of saying “start with a virtual server that only has Debian 12 on it.”

what i was trying to do here is automate building test servers – because i only get one run of Ardour before it fails to load Jack.

let’s ignore this whole part of the thread – it’s not that hard to install the current-release by hand if i need to. besides, current-release is Ardour8 and i need Ardour7 to work right, as that’s what apt installs on Debian 12.

the big thing is figuring out why i only get one run out of Ardour before it can’t start Jack and throws that “find a trout” error. a really helpful tool for that would be any kind of detailed diagnostic-mode of running Ardour so that maybe a log would give me a clue as to what’s going on. is there such a thing? and if so, how do i launch it?

#7

Why do you need to use what Debian has in the repository? Debian is known for being very slow to update packages, unless you are willing to run packages from the unstable repository.

Are you familiar with this page?
https://ardour.org/debugging_ardour.html

#8

On my system, Could not start Audio was always caused by pulseaudio or pipewire blocking ALSA and JACK.

For me, disabling pipewire and pulse audio when I wanted to use Ardour worked every time. No problems. No hangups. ALSA and JACK Worked flawlessly from then on.

systemctl --user stop pipewire.socket
systemctl --user stop pulseaudio.socket
systemctl --user stop pulseaudio.service

Also, I put the CPU into performance mode with :

echo performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor;

#9

  1. If it runs fine when JACK is already running, why not keep JACK running all the time? That’s worked well for me for over fifteen years.

  2. I’ve only been using linux since 1997, so maybe I don’t know all the old-guy ways of saying things, but: what the hell is a trout?

#10

Freshwater fish found in cool water. Popular with sport fishers, and useful for slapping C++ developers.
Although please do not slap any arbitrary developer with a trout, try to focus on the ones who throw exceptions without catching them.

#11

This is a reference to a funny error message:

1 Like
#12

Picture this… except for Programmers instead of TV Personalities

Seablade
#13

hi again!

wow… i can’t think of anything to add to the trout topic.

Schmitty – i loved your idea – tried it. no joy, but thanks!

Chris – long story on the version – the short version is that i value stability over everything else. THANKS for the pointer to the Debugging page. i knew i’d seen it somewhere but couldn’t get the search term right.

i ran Ardour in a gdb container. i’m a first-time user of gdb and the results imply that i’ve got some fix-up to do, so i’ll paste the term-session below. when i typed in the “thread apply all bt” command, i got nothing back. i’ll stick in some blank lines for readability.

thanks folks!

ardour --gdb

WARNING: Could not check your glib-2.0 for mutex locking atomic operations.

GNU gdb (Debian 13.1-3) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type “show copying” and “show warranty” for details.
This GDB was configured as “x86_64-linux-gnu”.
Type “show configuration” for configuration details.
For bug reporting instructions, please see:
https://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.

For help, type “help”.
Type “apropos word” to search for commands related to “word”…

Reading symbols from /usr/lib/ardour7/ardour-7.3.0~ds0…
(No debugging symbols found in /usr/lib/ardour7/ardour-7.3.0~ds0)

(gdb) handle SIG32 noprint nostop

Signal Stop Print Pass to program Description
SIG32 No No Yes Real-time event 32

(gdb) run

Starting program: /usr/lib/ardour7/ardour-7.3.0~ds0
BFD: error: /usr/lib/debug/.build-id/b5/94dc721d75112eb9f2aa7a2c0ae957f373d962.debug(.debug_info) is too large (0x15ef54 bytes)
warning: Can’t read data for section ‘.debug_info’ in file ‘/usr/lib/debug/.build-id/b5/94dc721d75112eb9f2aa7a2c0ae957f373d962.debug’
warning: Section .debug_aranges in /usr/lib/debug/.build-id/b5/94dc721d75112eb9f2aa7a2c0ae957f373d962.debug entry at offset 0 debug_info_offset 0 does not exists, ignoring .debug_aranges.

[Thread debugging using libthread_db enabled]
Using host libthread_db library “/lib/x86_64-linux-gnu/libthread_db.so.1”.
Ardour7.3.0~ds0 (built using 7.3.0~ds0-1 and GCC version 12.2.0)
[New Thread 0x7ffff02156c0 (LWP 45540)]

Ardour: [INFO]: Your system is configured to limit Ardour to 1048576 open files
Ardour: [INFO]: Loading system configuration file /etc/ardour7/system_config
Ardour: [INFO]: Loading user configuration file /root/.config/ardour7/config
[New Thread 0x7fffefdff6c0 (LWP 45541)]
Ardour: [INFO]: CPU vendor: AuthenticAMD
Ardour: [INFO]: AVX capable processor
Ardour: [INFO]: AVX with FMA capable processor
Ardour: [INFO]: CPU brand: AMD EPYC 7713 64-Core Processor
Ardour: [INFO]: Using AVX and FMA optimized routines
[New Thread 0x7fffef4f56c0 (LWP 45542)]
[New Thread 0x7fffeecf46c0 (LWP 45543)]
[New Thread 0x7fffee4f36c0 (LWP 45544)]
Ardour: [INFO]: Loading plugin meta data file /usr/share/ardour7/plugin_metadata/plugin_tags
Ardour: [INFO]: add_lrdf_data ‘/root/.config/ardour7/rdf:/usr/share/ardour7/rdf:/usr/local/share/ladspa/rdf:/usr/share/ladspa/rdf’
Ardour: [INFO]: read rdf_file ‘file:///usr/share/ladspa/rdf/ladspa.rdfs’
[New Thread 0x7fffed8b46c0 (LWP 45545)]
[Thread 0x7fffed8b46c0 (LWP 45545) exited]
[New Thread 0x7fffed8b46c0 (LWP 45546)]
[New Thread 0x7fffecb8c6c0 (LWP 45547)]
[New Thread 0x7fffcffff6c0 (LWP 45548)]
Ardour: [INFO]: Loading default ui configuration file /etc/ardour7/default_ui_config
Ardour: [INFO]: Loading user ui configuration file /root/.config/ardour7/ui_config
Xlib: extension “RANDR” missing on display “:1.0”.
Ardour: [INFO]: Loading 454 MIDI patches from /usr/share/ardour7/patchfiles
[New Thread 0x7fffcf7fe6c0 (LWP 45549)]
[New Thread 0x7fffceffd6c0 (LWP 45550)]
[Thread 0x7fffcf7fe6c0 (LWP 45549) exited]
[New Thread 0x7fffcf7fe6c0 (LWP 45551)]
[Thread 0x7fffceffd6c0 (LWP 45550) exited]
[New Thread 0x7fffceffd6c0 (LWP 45552)]
[Thread 0x7fffcf7fe6c0 (LWP 45551) exited]
[New Thread 0x7fffcf7fe6c0 (LWP 45553)]
[Thread 0x7fffceffd6c0 (LWP 45552) exited]
[Thread 0x7fffcf7fe6c0 (LWP 45553) exited]
Ardour: [INFO]: Loading color file /usr/share/ardour7/themes/dark-ardour.colors
Ardour: [INFO]: Loading ui configuration file /etc/ardour7/clearlooks.rc
[New Thread 0x7fffcf7fe6c0 (LWP 45554)]
[New Thread 0x7fffceffd6c0 (LWP 45555)]
[Thread 0x7fffcf7fe6c0 (LWP 45554) exited]
[New Thread 0x7fffcf7fe6c0 (LWP 45556)]
[Thread 0x7fffceffd6c0 (LWP 45555) exited]
[New Thread 0x7fffceffd6c0 (LWP 45557)]
[Thread 0x7fffcf7fe6c0 (LWP 45556) exited]
[New Thread 0x7fffcf7fe6c0 (LWP 45558)]
[Thread 0x7fffceffd6c0 (LWP 45557) exited]
[New Thread 0x7fffceffd6c0 (LWP 45559)]
[Thread 0x7fffcf7fe6c0 (LWP 45558) exited]
Ardour: [INFO]: Loading bindings from /etc/ardour7/ardour.keys
Loading ui configuration file /etc/ardour7/clearlooks.rc
[New Thread 0x7fffcf7fe6c0 (LWP 45560)]
[Thread 0x7fffceffd6c0 (LWP 45559) exited]
[New Thread 0x7fffceffd6c0 (LWP 45561)]
[Thread 0x7fffcf7fe6c0 (LWP 45560) exited]
[New Thread 0x7fffcf7fe6c0 (LWP 45562)]
[Thread 0x7fffceffd6c0 (LWP 45561) exited]
[New Thread 0x7fffceffd6c0 (LWP 45563)]
[Thread 0x7fffcf7fe6c0 (LWP 45562) exited]
[New Thread 0x7fffce7876c0 (LWP 45564)]
[Thread 0x7fffceffd6c0 (LWP 45563) exited]
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
[New Thread 0x7fffce7876c0 (LWP 45565)]
[Thread 0x7fffce7876c0 (LWP 45564) exited]
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
[Thread 0x7fffce7876c0 (LWP 45565) exited]
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
[New Thread 0x7fffce7876c0 (LWP 45566)]
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
[Thread 0x7fffce7876c0 (LWP 45566) exited]
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
[New Thread 0x7fffce7876c0 (LWP 45567)]
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
[Thread 0x7fffce7876c0 (LWP 45567) exited]
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Find a trout and repeatedly slap the nearest C++ who throws exceptions without catching them.
Ardour will likely crash now, giving you time to get the trout.
audio-midi engine setup failed.

[New Thread 0x7fffceffd6c0 (LWP 45568)]
[New Thread 0x7fffcf7fe6c0 (LWP 45569)]
[Thread 0x7fffceffd6c0 (LWP 45568) exited]
[New Thread 0x7fffceffd6c0 (LWP 45570)]
[Thread 0x7fffcf7fe6c0 (LWP 45569) exited]
[New Thread 0x7fffcf7fe6c0 (LWP 45571)]
[Thread 0x7fffceffd6c0 (LWP 45570) exited]
[Thread 0x7ffff02156c0 (LWP 45540) exited]
[Thread 0x7fffee4f36c0 (LWP 45544) exited]
[Thread 0x7fffeecf46c0 (LWP 45543) exited]
[Thread 0x7fffef4f56c0 (LWP 45542) exited]
[Thread 0x7fffed8b46c0 (LWP 45546) exited]
[Thread 0x7fffecb8c6c0 (LWP 45547) exited]
[Thread 0x7fffcf7fe6c0 (LWP 45571) exited]
[Thread 0x7fffefdff6c0 (LWP 45541) exited]
[Thread 0x7ffff0269d40 (LWP 45537) exited]
[Thread 0x7fffcffff6c0 (LWP 45548) exited]
[New process 45537]
[Inferior 1 (process 45537) exited normally]

(gdb) thread apply all bt

(gdb) exit

#14

I’m grateful to all for teaching me what a trout is! Pardon the interruption.

#15

That was a big source of confusion. Your description is almost completely the opposite of what the industry definition of “bare metal” is: a real, hardware server with no operating system at all.

FYI.

Cheers,

Keith

2 Likes
#16

Can you try in gdb:

handle SIG32 noprint nostop
start
catch throw
continue

and when ardour returns to the gdb prompt after the trout message:

bt

For faster turnaround times perhaps join us on IRC https://ardour.org/chat during US-eastern daytime.

Then again the real issue is “jack server is not running or cannot be started” and I have no idea why that would be.

#17

Have you tried to manually start JACk before starting ardour ?

#18

Shmitty – yep, Ardour runs if i manually start Jack. the reason i’m burrowing into this is because it’s a nice repeatable error which, when solved, may help identify other less-visible problems.

Robin – thanks for the invite to IRC. i’ll save that for a day when i need fast turnaround, however this isn’t that urgent. also thanks for the refinement of gdb. i ran with those this morning and here’s the change. meaningful, or just an artifact of how Ardour bails out when the Trout has been invoked?

Find a trout and repeatedly slap the nearest C++ who throws exceptions without catching them.
Ardour will likely crash now, giving you time to get the trout.

Thread 1 “ArdourGUI” hit Catchpoint 2 (exception thrown), 0x00007ffff54a90a1 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6

(gdb) continue

Continuing.
audio-midi engine setup failed.

i noticed that i can return Ardour to normal startup by deleting the config file. all the 1st runs i could figure out to try after doing this result in Ardour not starting Jack on the 2nd run. but at least i don’t have to stand up a new server each time to test. maybe that’s a clue? here are examples of the things i tried:

  • substitute the AudioMIDISetup section from the Ardour6 config file
  • try various templates
  • try closing without saving
  • try adding an audio track and changing Audio/Midi Setup

here’s a link to a typical config after a 1st run where i’ve set Audio to Jack, Dummy, Default, 48k, 512 and Midi to none.

#19

Instead of “continue”, type: thread apply all bt

#20

hi Paul,

ah! thanks! here’s the new stuff. the weird purple blobs are the forum software treating the double-colons around : : Thread: : as formatting…

Thread 1 “ArdourGUI” hit Catchpoint 2 (exception thrown), 0x00007ffff54a90a1 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) thread apply all bt

Thread 10 (Thread 0x7fffcffff6c0 (LWP 24342) “MIDNAMLoader”):
#0 0x00007ffff5ab6330 in xmlNewNsPropEatName () from /lib/x86_64-linux-gnu/libxml2.so.2
#1 0x00007ffff5b855d0 in ?? () from /lib/x86_64-linux-gnu/libxml2.so.2
#2 0x00007ffff5b88576 in xmlSAX2StartElementNs () from /lib/x86_64-linux-gnu/libxml2.so.2
#3 0x00007ffff5aa2049 in ?? () from /lib/x86_64-linux-gnu/libxml2.so.2
#4 0x00007ffff5aa35a1 in ?? () from /lib/x86_64-linux-gnu/libxml2.so.2
#5 0x00007ffff5aab5d0 in ?? () from /lib/x86_64-linux-gnu/libxml2.so.2
#6 0x00007ffff5aac5a8 in xmlParseElement () from /lib/x86_64-linux-gnu/libxml2.so.2
#7 0x00007ffff5aac9ea in xmlParseDocument () from /lib/x86_64-linux-gnu/libxml2.so.2
#8 0x00007ffff5ab234e in xmlCtxtReadFile () from /lib/x86_64-linux-gnu/libxml2.so.2
#9 0x00007ffff6ca39a4 in XMLTree::read_internal(bool) () from /usr/lib/ardour7/libpbd.so.4
#10 0x00007ffff7f533b7 in MIDI::Name::MIDINameDocument::MIDINameDocument(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) () from /usr/lib/ardour7/libmidipp.so.4
#11 0x00007ffff787ad02 in MIDI::Name::MidiPatchManager::load_midi_name_document(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) () from /usr/lib/ardour7/libardour.so.3
#12 0x00007ffff787b08b in MIDI::Name::MidiPatchManager::add_midnam_files_from_directory(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) () from /usr/lib/ardour7/libardour.so.3
#13 0x00007ffff787b393 in MIDI::Name::MidiPatchManager::load_midnams() () from /usr/lib/ardour7/libardour.so.3
#14 0x00007ffff6c851a6 in PBD::thread::_run(void*) () from /usr/lib/ardour7/libpbd.so.4
#15 0x00007ffff50d0044 in start_thread (arg=) at ./nptl/pthread_create.c:442
#16 0x00007ffff515061c in clone3 () at …/sysdeps/unix/sysv/linux/x86_64/clone3.S:81

–Type for more, q to quit, c to continue without paging–c
Thread 9 (Thread 0x7fffecb8d6c0 (LWP 24341) “DeviceList”):
#0 syscall () at …/sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x00007ffff6a573cf in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff74c450b in ARDOUR::AudioEngine::do_devicelist_update() () from /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff6c851a6 in PBD::thread::_run(void*) () from /usr/lib/ardour7/libpbd.so.4
#4 0x00007ffff50d0044 in start_thread (arg=) at ./nptl/pthread_create.c:442
#5 0x00007ffff515061c in clone3 () at …/sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 8 (Thread 0x7fffed8b36c0 (LWP 24340) “EngineWatchdog”):
#0 syscall () at …/sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x00007ffff6a573cf in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff74c6460 in ARDOUR::AudioEngine::do_reset_backend() () from /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff6c851a6 in PBD::thread::_run(void*) () from /usr/lib/ardour7/libpbd.so.4
#4 0x00007ffff50d0044 in start_thread (arg=) at ./nptl/pthread_create.c:442
#5 0x00007ffff515061c in clone3 () at …/sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 6 (Thread 0x7fffee4f36c0 (LWP 24338) “Analyzer”):
#0 syscall () at …/sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x00007ffff6a573cf in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff747dd87 in ARDOUR::Analyser::work() () from /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff6c851a6 in PBD::thread::_run(void*) () from /usr/lib/ardour7/libpbd.so.4
#4 0x00007ffff50d0044 in start_thread (arg=) at ./nptl/pthread_create.c:442
#5 0x00007ffff515061c in clone3 () at …/sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 5 (Thread 0x7fffeecf46c0 (LWP 24337) “PeakFileBuilder”):
#0 syscall () at …/sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x00007ffff6a573cf in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff7b744e9 in ?? () from /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff6c851a6 in PBD::thread::_run(void*) () from /usr/lib/ardour7/libpbd.so.4
#4 0x00007ffff50d0044 in start_thread (arg=) at ./nptl/pthread_create.c:442
#5 0x00007ffff515061c in clone3 () at …/sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 4 (Thread 0x7fffef4f56c0 (LWP 24336) “PeakFileBuilder”):
#0 syscall () at …/sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x00007ffff6a573cf in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff7b744e9 in ?? () from /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff6c851a6 in PBD::thread::_run(void*) () from /usr/lib/ardour7/libpbd.so.4
#4 0x00007ffff50d0044 in start_thread (arg=) at ./nptl/pthread_create.c:442
#5 0x00007ffff515061c in clone3 () at …/sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 3 (Thread 0x7fffefdff6c0 (LWP 24335) “LXVSTEventLoop”):
#0 0x00007ffff5116385 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7fffefdfe6e0, rem=0x7fffefdfe6f0) at …/sysdeps/unix/sysv/linux/clock_nanosleep.c:48
#1 0x00007ffff511ac93 in __GI___nanosleep (req=, rem=) at …/sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x00007ffff6a2e77f in g_usleep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x0000555556622854 in ?? ()
#4 0x00007ffff50d0044 in start_thread (arg=) at ./nptl/pthread_create.c:442
#5 0x00007ffff515061c in clone3 () at …/sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 2 (Thread 0x7ffff02136c0 (LWP 24334) “Trigger Worker”):
#0 0x00007ffff514305f in __GI___poll (fds=0x7ffff02127c0, nfds=1, timeout=-1) at …/sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007ffff6c5cef8 in CrossThreadChannel::poll_for_request() () from /usr/lib/ardour7/libpbd.so.4
#2 0x00007ffff6c5cf7a in CrossThreadChannel::receive(char&, bool) () from /usr/lib/ardour7/libpbd.so.4
#3 0x00007ffff7bc61c1 in ARDOUR::TriggerBoxThread::thread_work() () from /usr/lib/ardour7/libardour.so.3
#4 0x00007ffff6c84903 in ?? () from /usr/lib/ardour7/libpbd.so.4
#5 0x00007ffff50d0044 in start_thread (arg=) at ./nptl/pthread_create.c:442
#6 0x00007ffff515061c in clone3 () at …/sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 1 (Thread 0x7ffff0267d40 (LWP 24333) “ArdourGUI”):
#0 0x00007ffff54a90a1 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x0000555555a31a36 in ?? ()
#2 0x0000555555e27be3 in ?? ()
#3 0x0000555555e2d3d9 in ?? ()
#4 0x0000555555e35255 in ?? ()
#5 0x0000555555bd9a45 in ?? ()
#6 0x00007ffff6d26736 in Gtkmm2ext::UI::run(Receiver&) () from /usr/lib/ardour7/libgtkmm2ext.so.0
#7 0x0000555555b1b4aa in main ()