[15:33] Eickmeyer: Carla 2.2 rc2 seems to have fixed the segfault problem with zita-ajbridge [16:13] OvenWerks: Good to know. Should I yeet it into backports? [16:19] Eickmeyer[m]: scratch that [16:19] Uhhhh.... [16:19] it worked fine for 4 or 5 times [16:19] Yikes. [16:19] soon as I told falktx it seems to be working I get the same problem. [16:20] Welp... [16:21] It seems that with the system having been running for a few days it worked fine for a few tries. but when I rebooted it it fails first time every time. [16:21] That is odd. [16:22] I mean, why would a reboot affect it? [16:24] general system activity higher? I don't know. I am running htop and it doesn't seem to be high. [16:25] the problem does show up within 5 tries even after system has been up a while [16:25] How spaced-out are these tries? Like, what's the interval? [16:26] close. within 2 or 3 minutes [16:26] I am not using controls to start/stop zita-ajbridge [16:26] Ok, so not like spamming it. [16:26] I am doing it manually, so two terminals one for a2j and one for j2a [16:27] So plug in, start one then start 2. check that jack_lsp shows ports [16:27] (or Carla shows ports) [16:28] unplug, make input terminal focus, ctrl-c make output terminal focus, ctrl-c [16:30] Is it just having an error monitoring dbus, you think? [16:30] I can do this as many times as I like with Carla closed. zita-ajbridge stops normally. but with Carla open, zita-ajbridge segfaults on ctrl-c (sigint) jack_lsp fails to finish (hangs after showing ports) [16:30] dbus should have nothing to do with this [16:30] Ok, just spitballing. [16:31] this is all jack api stuff [16:31] Maybe it's because you have two items looking at the connections at once (jack_lsp and Carla)? [16:32] Basically, making the same jack api calls? [16:32] That would be a jack bug, but carla 2.1 does not have this problem, I can use qjackctl and jack_lsp [16:33] I get the same problem even if I don't run jack_lsp and just try to move one of carlas jack port items [16:36] Eickmeyer[m]: it should be ok to have 5 clients making those api calls [16:36] Yeah, good point. [16:39] Alsa_in has high cpu on device unplug, Alsa_out just quits with "Write error: No such device [16:40] So Alsa_in is perhaps broken too. [16:55] Wouldn't surprise me. [16:56] * Eickmeyer[m] uploaded an image: 4e8x5b.jpg (89KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/BSgyyjLltEkgWWqTifvLogyc/4e8x5b.jpg > [16:56] Just a little fun. :) [17:06] Eickmeyer[m]: there was a while where it was pretty much for some things. It is unfortunate that people just added the whole thing rather than cherry picking. It is also unfortunate that ladish was auto started by all the kx tools [17:07] Yep, indeed. Now ladish is a thing of the past. [17:07] Studio was in a rather bad state just before you stepped in [17:07] Yeah, I know, which is part of why I try to steer people away from 18.04. [17:08] * OvenWerks doesn't have a choice on that one... last thing to support his laptop [17:10] Yeah, unfortunately. [17:14] That laptop will probably move to debian next [17:17] It will be sort of Studio-ized with ardour at least and a good kernel. [20:20] Eickmeyer[m]: the problem with Carla 2.2 is also present in falktx' working Catia split as well but not in catia that comes with latest cadence. [20:23] falktx and I have been able to isolate this to one portion of code but because Fons is well known to use only jackd1 (and is even possibly working on a "Jackd3" extended from jackd1, not jackd2, it could well be a jackd1/2 difference