Looks as though this was reported [1], and turns out is actually a bug in systemd <=240 [2]. Shows as fixed in systemd 241 [3].
[1] https://github.com/jackaudio/jack2/issues/429 [1] https://github.com/systemd/systemd/issues/11386 [2] https://github.com/systemd/systemd/pull/11448 ** Bug watch added: github.com/jackaudio/jack2/issues #429 https://github.com/jackaudio/jack2/issues/429 ** Also affects: jack via https://github.com/jackaudio/jack2/issues/429 Importance: Unknown Status: Unknown ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #11386 https://github.com/systemd/systemd/issues/11386 ** No longer affects: jack ** Changed in: jackd2 (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Also affects: systemd via https://github.com/systemd/systemd/issues/11386 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
