[SOLVED] Ardour8 not starting up - Segmentation fault (core dumped)

electronarchy · 2024-06-14 15:07:18

Ardour hasn't been updated since April, but just this week stopped working. Must be due to recent updates. I am running KDE on arch.

I have tried rolling back a few packages with no luck. I don't know how to find more information on this error.
I tried moving configs to backup locations and reinstalling.
This is frustrating. I need my DAW back.

When I boot ardour8 from terminal, this is the ouput:

Ardour8.6.0 (built using 8.6 and GCC version 13.2.1 20230801)
Ardour: [INFO]: Your system is configured to limit Ardour to 524288 open files
Ardour: [INFO]: Loading user configuration file /home/archy/.config/ardour8/config
Ardour: [INFO]: CPU vendor: GenuineIntel
Ardour: [INFO]: AVX capable processor
Ardour: [INFO]: AVX with FMA capable processor
Ardour: [INFO]: CPU brand: Intel(R) Core(TM) Ultra 7 155H
Ardour: [INFO]: Using AVX and FMA optimized routines
Ardour: [INFO]: Loading plugin meta data file /usr/share/ardour8/plugin_metadata/plugin_tags
Ardour: [INFO]: Loading plugin statistics file /home/archy/.config/ardour8/plugin_metadata/plugin_stats
Ardour: [INFO]: add_lrdf_data '/home/archy/.config/ardour8/rdf:/usr/share/ardour8/rdf:/usr/local/share/ladspa/rdf:/usr/share/ladspa/rdf'
Ardour: [INFO]: read rdf_file 'file:///usr/share/ladspa/rdf/caps.rdf'
Segmentation fault (core dumped)

Last edited by electronarchy (2024-06-14 16:12:03)

WorMzy · 2024-06-14 15:30:07

Seems to be a problem with caps -- ardour launches fine here without caps installed, but segfaults with it present. Short term solution may be to remove caps from your system, but long-term, you probably want to open a bug report under ardour's bug tracker.

electronarchy · 2024-06-14 16:10:33

WorMzy wrote:

Seems to be a problem with caps

good catch, thank you!! once I removed caps I had a segmentation fault again with swf-plugins, then I removed that and it's starting up again.

where do you think the bug is, with ardour, or these plugins? or possibly a recent update to pipewire or something?
Ardour hasn't seen an update since April, and this problem just came up for me this week.

thanks for the quick fix though! marking solved.

WorMzy · 2024-06-14 16:46:09

Hm, digging deeper (using 'ardour8 -g' to run with gdb), the crash seems to originate within the libxml2 parser:

Thread 1 "ardour-8.6.0" received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff39d094a in raptor_libxml_update_document_locator (sax2=<optimized out>, 
    locator=locator@entry=0x55555675cc20) at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_libxml.c:342
#2  0x00007ffff39d097a in raptor_sax2_update_document_locator (sax2=<optimized out>, 
    locator=locator@entry=0x55555675cc20) at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_sax2.c:620
#3  0x00007ffff39d82e3 in raptor_rdfxml_update_document_locator (rdf_parser=0x55555675cc10)
    at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_rdfxml.c:3154
#4  raptor_rdfxml_start_element_handler (user_data=0x55555675cc10, xml_element=0x55555673b4d0)
    at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_rdfxml.c:574
#5  0x00007ffff39d72ac in raptor_sax2_start_element (user_data=<optimized out>, name=<optimized out>, 
    atts=<optimized out>) at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_sax2.c:835
#6  raptor_sax2_start_element (user_data=<optimized out>, name=<optimized out>, atts=<optimized out>)
    at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_sax2.c:627
#7  0x00007ffff5eb6b6b in xmlParseStartTag (ctxt=ctxt@entry=0x555556765730)
    at /usr/src/debug/libxml2/libxml2/parser.c:8471
#8  0x00007ffff5ebccb1 in xmlParseTryOrFinish (ctxt=0x555556765730, terminate=1)
    at /usr/src/debug/libxml2/libxml2/parser.c:11134
#9  xmlParseChunk (ctxt=0x555556765730, chunk=<optimized out>, size=<optimized out>, terminate=1)
    at /usr/src/debug/libxml2/libxml2/parser.c:11545
#10 xmlParseChunk (ctxt=0x555556765730, chunk=<optimized out>, size=<optimized out>, terminate=1)
    at /usr/src/debug/libxml2/libxml2/parser.c:11509
#11 0x00007ffff39d372e in raptor_sax2_parse_chunk (sax2=0x555556741840, 
    buffer=0x55555675ce38 "\n\t\t\t\t\t\t\t\trdf:value=\"0\" \n\t\t\t\t\t\t\t\tladspa:hasLabel=\"lowshelve\" />\n\t\t\t\t\t\t</ladspa:hasPoint> \n\t\t\t\t\t\t<ladspa:hasPoint><ladspa:Point \n\t\t\t\t\t\t\t\trdf:value=\"1\" \n\t\t\t\t\t\t\t\tladspa:hasLabel=\"band\" />\n\t\t\t\t\t\t</ladspa:h"..., len=<optimized out>, is_end=1)
    at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_sax2.c:569
#12 0x00007ffff39dccf1 in raptor_rdfxml_parse_chunk (rdf_parser=0x55555675cc10, buffer=<optimized out>, 
    len=<optimized out>, is_end=1) at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_rdfxml.c:1172
#13 0x00007ffff39c837a in raptor_parser_parse_file_stream (rdf_parser=rdf_parser@entry=0x55555675cc10, 
    stream=stream@entry=0x5555566e1830, filename=filename@entry=0x555556744a40 "/usr/share/ladspa/rdf/caps.rdf", 
    base_uri=base_uri@entry=0x55555675cb90) at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_parse.c:554
#14 0x00007ffff39c8666 in raptor_parser_parse_file (rdf_parser=0x55555675cc10, uri=0x55555675cb90, 
    base_uri=0x55555675cb90) at /usr/src/debug/raptor/raptor2-2.0.16/src/raptor_parse.c:616
#15 0x00007ffff5207d69 in lrdf_read_file_intl () from /usr/lib/liblrdf.so.2
#16 0x00007ffff5208f98 in lrdf_read_file () from /usr/lib/liblrdf.so.2
#17 0x00007ffff77c438a in ARDOUR::PluginManager::add_lrdf_data (this=this@entry=0x5555566b88e0, path=...)
    at /usr/include/c++/13.2.1/bits/basic_string.h:222
#18 0x00007ffff77cb878 in ARDOUR::PluginManager::PluginManager (this=<optimized out>, this=<optimized out>)
    at ../libs/ardour/plugin_manager.cc:278
#19 0x00007ffff77cbfdf in ARDOUR::PluginManager::instance () at ../libs/ardour/plugin_manager.cc:177
#20 0x00007ffff768ed38 in ARDOUR::init (try_optimization=<optimized out>, localedir=<optimized out>, 
    with_gui=with_gui@entry=true) at ../libs/ardour/globals.cc:718
#21 0x000055555596c8ba in main (argc=<optimized out>, argv=<optimized out>)
    at /usr/include/c++/13.2.1/bits/basic_string.h:222

Libxml2 was recently (June 12th) updated to 2.13.0: https://gitlab.archlinux.org/archlinux/ … 68fd9ac942
Downgrading to the previous version (2.12.7) allows ardour to launch even with caps installed.

So this is likely a regression in libxml2, not ardour as I first suspected.

Scimmia · 2024-06-14 17:03:18

This libxml2 update has caused issues elsewhere as well. https://gitlab.archlinux.org/archlinux/ … -/issues/1 for example.

Arch Linux

#1 2024-06-14 15:07:18

[SOLVED] Ardour8 not starting up - Segmentation fault (core dumped)

#2 2024-06-14 15:30:07

Re: [SOLVED] Ardour8 not starting up - Segmentation fault (core dumped)

#3 2024-06-14 16:10:33

Re: [SOLVED] Ardour8 not starting up - Segmentation fault (core dumped)

#4 2024-06-14 16:46:09

Re: [SOLVED] Ardour8 not starting up - Segmentation fault (core dumped)

#5 2024-06-14 17:03:18

Re: [SOLVED] Ardour8 not starting up - Segmentation fault (core dumped)

Board footer