Ardour 3.5 doesn't start

Installation & Configuration Linux
#1

I don’t know if this is a configuration issue, as the installation is supposed to be so straightforward… BTW after a handful of seconds the splash screen disappears and Ardour doesn’t start.

This is what I get if I start it from a shell:

luca@Shub-Niggurath:~$ /opt/Ardour-3.5-dbg/bin/ardour3 Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 84: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 84: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 93: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 93: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 102: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 102: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 34: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 63: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 73: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 73: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 73: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 84: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 84: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 84: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 93: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 75: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 75: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 10: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 16: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 61: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 96: Having multiple values in isn't supported and may not work as expected Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 14: out of memory Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 23: out of memory Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 32: out of memory Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf", line 9: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf", line 21: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf", line 9: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf", line 21: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-loma-synthetic.conf", line 12: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf", line 9: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf", line 21: Having multiple values in isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf", line 11: Having multiple values in isn't supported and may not work as expected bnd txt domain [gtk2_ardour3] to /opt/Ardour-3.5-dbg/share/locale Ardour3.5 (built using 3.5 and GCC version 4.4.6) ardour: [INFO]: Your system is configured to limit Ardour to only 4096 open files ardour: [INFO]: Ardour: impossibile leggere il file di configurazione di sistema "/opt/Ardour-3.5-dbg/etc/ardour_system.rc" Ardour: impossibile la lettura del file di configurazione "/home/luca/.config/ardour3/ardour.rc" Using SSE optimized routines ardour: [INFO]: Carico il file di configurazione base per /opt/Ardour-3.5-dbg/etc/ardour3_ui_default.conf Carico il file di configurazione dell'interfaccia utente /opt/Ardour-3.5-dbg/etc/ardour3_ui.conf

(ardour-3.5:5214): GLib-GObject-WARNING **: Attempt to add property gtkmm__CustomObject_N9Gtkmm2ext25CellRendererColorSelectorE::color after class was initialised
ardour: [INFO]: Loading ui configuration file /opt/Ardour-3.5-dbg/etc/ardour3_ui_dark.rc
Jack: JackClient::SetupDriverSync driver sem in flush mode
Jack: JackPosixSemaphore::Connect name = jack_sem.1000_default_ardourprobe
Jack: JackPosixSemaphore::Connect sem_getvalue 0
Jack: Clock source : system clock via clock_gettime
Jack: JackLibClient::Open name = ardourprobe refnum = 3
Jack: jack_client_close
Jack: JackClient::Close ref = 3
Jack: JackClient::Deactivate
Jack: JackSocketClientChannel::Stop
Jack: JackPosixThread::Kill
Jack: JackClientSocket::Close
Jack: JackClientSocket::Close
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_ardourprobe
Jack: JackLibClient::~JackLibClient
Jack: JackShmReadWritePtr1::~JackShmReadWritePtr1 3
Jack: Succeeded in unlocking 384 byte memory area
Jack: JackLibGlobals Destroy 3153e20
Jack: ~JackLibGlobals
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_system
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_freewheel
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_qjackctl
Jack: no message buffer overruns
Jack: JackPosixThread::Stop
Jack: ThreadHandler: exit
Jack: JackShmReadWritePtr::~JackShmReadWritePtr 1
Jack: Succeeded in unlocking 1040 byte memory area
Jack: JackShmReadWritePtr::~JackShmReadWritePtr 0
Jack: Succeeded in unlocking 82246176 byte memory area
Jack: jack_client_close res = 0
Found 0 along /home/luca/.config/ardour3/templates:/opt/Ardour-3.5-dbg/share/templates
run dialog
Announcement is:
Jack: jack_client_open ardour
Jack: JackLibGlobals Init 0
Jack: JackLibGlobals
Jack: Create non RT thread
Jack: ThreadHandler: start
Jack: JackSocketClientChannel::ServerCheck = default
Jack: Connect: addr.sun_path /dev/shm/jack_default_1000_0
Jack: JackClientSocket::Close
Jack: JackLibClient::JackLibClient table = 36db0d0
Jack: JackLibClient::Open name = ardour
Jack: JackSocketClientChannel::Open name = ardour
Jack: Connect: addr.sun_path /dev/shm/jack_default_1000_0
Jack: Bind: addr.sun_path /dev/shm/jack_ardour_1000_0
Jack: JackSocketClientChannel::Start
Jack: Create non RT thread
Jack: ThreadHandler: start
Jack: JackSocketClientChannel::Init
Jack: JackServerSocket::Close /dev/shm/jack_ardour_1000_0
Jack: JackClient::ClientNotify ref = 0 name = system notify = 0
Jack: JackClient::AddClient name = system, ref = 0
Jack: JackPosixSemaphore::Connect name = jack_sem.1000_default_system
Jack: JackPosixSemaphore::Connect sem_getvalue 0
Jack: JackClient::ClientNotify ref = 1 name = freewheel notify = 0
Jack: JackClient::AddClient name = freewheel, ref = 1
Jack: JackPosixSemaphore::Connect name = jack_sem.1000_default_freewheel
Jack: JackPosixSemaphore::Connect sem_getvalue 0
Jack: JackClient::ClientNotify ref = 2 name = qjackctl notify = 0
Jack: JackClient::AddClient name = qjackctl, ref = 2
Jack: JackPosixSemaphore::Connect name = jack_sem.1000_default_qjackctl
Jack: JackPosixSemaphore::Connect sem_getvalue 0
Jack: JackShmReadWritePtr::Init 1 4294967295
Jack: Succeeded in locking 1040 byte memory area
Jack: JackShmReadWritePtr::Init 0 4294967295
Jack: Succeeded in locking 82246176 byte memory area
Jack: JackShmReadWritePtr1::Init 3 4294967295
Jack: Succeeded in locking 384 byte memory area
Jack: JackClient::SetupDriverSync driver sem in flush mode
Jack: JackPosixSemaphore::Connect name = jack_sem.1000_default_ardour
Jack: JackPosixSemaphore::Connect sem_getvalue 0
Jack: Clock source : system clock via clock_gettime
Jack: JackLibClient::Open name = ardour refnum = 3
Jack: jack_set_graph_order_callback ext_client 36da420 client 36da420
Jack: jack_set_thread_init_callback ext_client 36da420 client 36da420
Jack: JackClient::Activate
Jack: JackClient::StartThread : period = 5333 computation = 100 constraint = 5333
Jack: Create non RT thread
Jack: ThreadHandler: start
Jack: JackClient::kBufferSizeCallback buffer_size = 256
Jack: JackClient::Init calling client thread init callback
Jack: JackPosixThread::AcquireRealTimeImp priority = 84
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 2
Jack: JackClient::kActivateClient name = ardour ref = 3
Jack: JackClient::Init calling client thread init callback
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 4
Jack: JackClient::kGraphOrderCallback
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 4
Jack: JackClient::kGraphOrderCallback
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Scanning folders for bundled LV2s: /opt/Ardour-3.5-dbg/lib/LV2
lilv_plugin_load_ports_if_necessary(): error: Plugin http://home.gna.org/lv2vocoder/1 port symbol `600’ is invalid

(ardour-3.5:5214): GLib-GObject-WARNING **: Attempt to add property gtkmm__CustomObject_N9Gtkmm2ext23CellRendererPixbufMultiE::active after class was initialised
Jack: JackClient::TransportLocate pos = 0
Jack: RequestNewPos pos = 0
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 9
Jack: JackClient::kPortRegistrationOn port_index = 7
Jack: JackClient::PortRegister ref = 3 name = ardour:LTC In/audio_in 1 type = 32 bit float mono audio port_index = 7
Jack: JackClient::PortDisconnect src = 7
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 4
Jack: JackClient::kGraphOrderCallback
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackGraphManager::RecalculateLatency port_index = 7
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackClient::PortDisconnect src = 7
Jack: JackClient::Connect src = system:capture_1 dst = ardour:LTC In/audio_in 1
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 11
Jack: JackClient::kPortConnectCallback src = 1 dst = 7
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 9
Jack: JackClient::kPortRegistrationOn port_index = 8
Jack: JackClient::PortRegister ref = 3 name = ardour:LTC Out/audio_out 1 type = 32 bit float mono audio port_index = 8
Jack: JackClient::PortDisconnect src = 8
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 4
Jack: JackClient::kGraphOrderCallback
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackGraphManager::RecalculateLatency port_index = 7
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackGraphManager::RecalculateLatency port_index = 8
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 9
Jack: JackClient::kPortRegistrationOn port_index = 9
Jack: JackClient::PortRegister ref = 3 name = ardour:click/audio_out 1 type = 32 bit float mono audio port_index = 9
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 9
Jack: JackClient::kPortRegistrationOn port_index = 10
Jack: JackClient::PortRegister ref = 3 name = ardour:click/audio_out 2 type = 32 bit float mono audio port_index = 10
Jack: JackClient::PortDisconnect src = 9
Jack: JackClient::PortDisconnect src = 10
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 4
Jack: JackClient::kGraphOrderCallback
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackGraphManager::RecalculateLatency port_index = 7
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackGraphManager::RecalculateLatency port_index = 8
Jack: JackGraphManager::RecalculateLatency port_index = 9
Jack: JackGraphManager::RecalculateLatency port_index = 10
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 9
Jack: JackClient::kPortRegistrationOn port_index = 11
Jack: JackClient::PortRegister ref = 3 name = ardour:MIDI control in type = 8 bit raw midi port_index = 11
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 9
Jack: JackClient::kPortRegistrationOn port_index = 12
Jack: JackClient::PortRegister ref = 3 name = ardour:MIDI control out type = 8 bit raw midi port_index = 12
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 9
Jack: JackClient::kPortRegistrationOn port_index = 13
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 4
Jack: JackClient::kGraphOrderCallback
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackGraphManager::RecalculateLatency port_index = 7
Jack: JackGraphManager::RecalculateLatency port_index = 11
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackGraphManager::RecalculateLatency port_index = 8
Jack: JackGraphManager::RecalculateLatency port_index = 9
Jack: JackGraphManager::RecalculateLatency port_index = 10
Jack: JackGraphManager::RecalculateLatency port_index = 12
Jack: JackClient::PortRegister ref = 3 name = ardour:MMC in type = 8 bit raw midi port_index = 13
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 9
Jack: JackClient::kPortRegistrationOn port_index = 14
Jack: JackClient::PortRegister ref = 3 name = ardour:taglia type = 8 bit raw midi port_index = 14
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 9
Jack: JackClient::kPortRegistrationOn port_index = 15
Jack: JackClient::PortRegister ref = 3 name = ardour:MTC in type = 8 bit raw midi port_index = 15
Failed to register port “taglia”, reason is unknown from here
Jack: JackClient::PortUnRegister port_index = 8
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 10
Jack: JackClient::kPortRegistrationOff port_index = 8
Jack: JackClient::PortUnRegister port_index = 7
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 12
Jack: JackClient::kPortDisconnectCallback src = 1 dst = 7
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 10
Jack: JackClient::kPortRegistrationOff port_index = 7
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 4
Jack: JackClient::kGraphOrderCallback
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackGraphManager::RecalculateLatency port_index = 11
Jack: JackGraphManager::RecalculateLatency port_index = 13
Jack: JackGraphManager::RecalculateLatency port_index = 15
Jack: JackClient::ClientNotify ref = 3 name = ardour notify = 18
Jack: JackGraphManager::RecalculateLatency port_index = 9
Jack: JackGraphManager::RecalculateLatency port_index = 10
Jack: JackGraphManager::RecalculateLatency port_index = 12
Jack: JackGraphManager::RecalculateLatency port_index = 14
GLib (gthread-posix.c): Unexpected error from C library during ‘pthread_mutex_lock’: Argomento non valido. Aborting.
Annullato (core dump creato)
luca@Shub-Niggurath:~$

#2

Uh, Ardour 3.4 is working fine as always.

#3

99% of what you posted is just noise. The only thing that matters is:

GLib (gthread-posix.c): Unexpected error from C library during ‘pthread_mutex_lock’: Argomento non valido. Aborting.

This is a system specific error which does not happen on (many) other people’s system. It will be hard to debug without you (1) filing a bug report in the right place (tracker.ardour.org) and (2) following the steps outlined in http://ardour.org/debugging_ardour

#4

Yep. Thanks!

#5

Have you been able to resolve? Because I have the same problem.

How I can download Ardour 3.4 again? This would work just fine.

Thank you very much.

#6

I haven’t resolver it yet. I am just about filling a bug report.

I don’t know where to download the previous 3.x versions, I still had it in my HD, so I simply installed it back. I could post a wetransfer link here, but I don’t actually know if it is forbidden or not.

#7

As soon as I get the registration confirmation email I’ll fill the bug report.

#8

@puppet if you don’t get it fairly quick (Within an hour or so) let us know.

 Seablade
#9

I havent’ got the email so far… I checked the spam receptacle and it was empty.

#10

@puppet

Ill have to point paul to it then, user management is one of the things I can’t do sorry.

  Seablade
#11

Ok, thank you. I’ll wait to be solved.

But if possible (and legal) someone provide the download link for version 3.4, much appreciate it.

Thank you very much.

#12

@puppet

If you feel comfortable doing so, can you confirm the email address you are expecting it at?

     Seablade
#13

no problem :wink: puppet.trash(at)alice.it

On wednesday morning I’ll leave for a few days because of my actual job (not music unfortunately) so tomorrow evening is the deadline for me to post.

#14

Hi guys
I haven’t received my registration email yet. Sould I try again?

#15

@puppet

I pointed Paul to this, it is just a matter of when he gets time is all, sorry. Thanks for being willing to help!

   Seablade
#16

The mail was sent out. If you didn’t receive it, you’ll need to try again.

#17

Well guys this is strange indeed! No email yet, so I tried to subscribe once again but I am told that my username has already been used. I’ll try again when I’ll coma back from my job journey, and I’ll let you know if I got the email.

BTW you don’r really have to thank me, I’m just a user, YOU are the heroes to save the day! :wink:

#18

The only update I can give is that 3.5.14 behaves the same.

#19

Same result here. After a few seconds the splash screen disappears and then nothing.

Ardour 3.5.14 (version 3.4 works fine)

Failed to register port "utgång", reason is unknown from here
GLib (gthread-posix.c): Unexpected error from C library during 'pthread_mutex_lock': Ogiltigt argument.  Aborting.
Avbruten (SIGABRT)

Jack 1.9.9

01:45:48.202 JACK connection graph change.
01:46:26.165 JACK connection graph change.
01:46:27.141 JACK connection graph change.
port_name "ardour:utgång" already exists
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = ardour was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot read socket fd = 14 err = Connection reset by peer
Could not read notification result
NotifyClient fails name = ardour notification = 18 val1 = 0 val2 = 0
01:46:27.197 XRUN callback (10).
Cannot write socket fd = 14 err = Broken pipe
CheckRes error
Could not write notification
NotifyClient fails name = ardour notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 14 err = Broken pipe
CheckRes error
..
#20

ekabjan: thanks to a user who showed up on IRC, we were able to figure out the cause of this error. It is caused by “fuzzy translations”. If you run ardour in english it will work. the next release will have this corrected.