Hello Tjeerd,
If this issue still exists on your system, you might try
to rename $HOME/.audacity-data to test if it depends on
some settings stored there.
If it still crashes then you might start it by following
and forward the output:
$ catchsegv audacity
Better would be if you could install the packages:
systemd-coredump gdb valgrind audacity-dbgsym
The last one is in a different repository described here [1].
Then some more information should appear after
a crash in 'journalctl --no-pager'.
Also running audacity by following could give some pointer:
$ valgrind audacity
Kind regards,
Bernhard
[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
