[00:09] <OvenWerks> Eickmeyer: I am also having trouble with 1.9.19 in 21.10
[00:13] <OvenWerks> Eickmeyer: autojack seems to hang because I get no errors. I just stops after creating it's own jack client
[00:17] <OvenWerks> hmm, autojack does not show the jack client as being actually created successfully, but the jack log does
[00:18] <OvenWerks> Carla crash when starting the "audio engine"
[00:23] <OvenWerks> OK, lets reboot
[00:29] <OvenWerks> Eickmeyer: ok, I first stopped jack in controls. Then rebooted. (this made sure autojack did nothing with jack after reboot)
[00:29] <OvenWerks> Then I started jack with jack_control start
[00:32] <OvenWerks> Then I used jack_lsp to list jack's ports... $ jack_lsp
[00:32] <OvenWerks> Segmentation fault (core dumped)
[00:34] <OvenWerks> Ok so look at the jack log: everything looks normal till: New client 'PulseAudio JACK Sink' with PID 1764
[00:34] <OvenWerks> Thu Jul 22 17:27:29 2021: Client 'PulseAudio JACK Sink' with PID 1764 is out
[00:36] <OvenWerks> Then pulse tries again... and starts spewing xruns, jack then fails to find pulse's port
[00:37] <OvenWerks> finally pulse gives up... 
[00:39] <OvenWerks> OK, so I will reboot again. and remove the jackdbus detect module before starting jackdbus next time.
[00:44] <OvenWerks> Eickmeyer: jackd 1.9.19 as built in 21.10 is thge problem.
[00:45] <OvenWerks> another fresh reboot, pactl unload-module module-jackdbus-detect, jack_control start and pulse jack sink does not try to load. run jack_lsp and it crashes.
[00:46] <OvenWerks> Eickmeyer: note also that the python jacklib also fails when creating a client.
[00:56] <OvenWerks> Eickmeyer: my guess would be that one of the deps is a different version... does 1.1.17 use all the same deps? That would leave  libdb as the only extra thing. What is the difference in versions for that lib from 20.04 to 20.10?
[01:00] <OvenWerks> but that package is the same version all the way through.
[01:06] <OvenWerks> Eickmeyer: using jackd instead of jackdbus also fails
[01:07] <OvenWerks> Eickmeyer: that was incorrectjackd does does not fail, but jack clients also fail on jackd
[01:08] <OvenWerks> 1.1.17 was working fine
[01:18] <OvenWerks> Eickmeyer: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325
[01:19] <OvenWerks> Eickmeyer:  you may wish to hit the "this bug affects me" link.
[02:29] <Eickmeyer> OvenWerks: If you check the maintainer field on that, you'll find it's me, so the only thing we can do is report upstream to falktx.
[02:30] <Eickmeyer> Also, it's 1.9.19 not 1.1.19.
[02:35] <OvenWerks> oops
[02:36] <OvenWerks> probably is was the 1 in 19 I saw.
[02:41] <Eickmeyer> Probably.
[02:41] <Eickmeyer> Either way... https://github.com/jackaudio/jack2/issues/776
[02:41] <Eickmeyer> Just filed this.
[02:43] <Eickmeyer> OvenWerks: But yeah, I did the upload of 1.9.19, which makes me automatically the maintainer, which means the buck stops here for that bug. Hence, filed upstream.
[02:44] <OvenWerks> so back to 1.9.17?
[02:45] <Eickmeyer> That can't be done without some versioning gymnastics and a bunch of egg on my face, so I hope falktx might be able to fix it.
[02:45] <OvenWerks> did he change the access to memlock etc?
[02:46] <Eickmeyer> Not 100% sure, especially since it is only problematic against kernel 5.11 and not kernel 5.8.
[02:46] <Eickmeyer> Might even be a dbus difference.
[02:48] <Eickmeyer> If it doesn't get fixed before feature freeze, we'll downgrade it back to 1.9.17 with said versioning gymnastics.
[02:51] <Eickmeyer> OvenWerks: Also, I'm out in Idaho today through Sunday due to a death in the family.
[02:53] <OvenWerks> no worries, take care. I will keep my release schedule for next monday, I think.
[02:54] <Eickmeyer> OvenWerks: Ok, sounds good. Shoot me an email if you need anything because I probably won't respond to IRC.