Jack clients have segmentation fault when trying to connect to jackd

Bug #1937325 reported by Len Ovens
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
jackd2 (Ubuntu)
Fix Released
Critical
Erich Eickmeyer

Bug Description

Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. This is specific to jackd2 1.9.19, jackd 1.9.17 does not have this problem.

jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does not.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21
Uname: Linux 5.11.0-20-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Thu Jul 22 18:09:18 2021
InstallationDate: Installed on 2021-06-15 (37 days ago)
InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613)
SourcePackage: jackd2
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Len Ovens (len-ovenwerks) wrote :
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in jackd2 (Ubuntu):
status: New → Confirmed
description: updated
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :
Changed in jackd2 (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
assignee: nobody → Erich Eickmeyer  (eeickmeyer)
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Changed to critical as this is a blocking bug for Ubuntu Studio 21.10's release.

Changed in jackd2 (Ubuntu):
importance: High → Critical
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

New information: Rebuilds of 1.9.17 and builds of 1.9.18 in impish result in the same issue, meaning there is likely a build-time dependency incompatibility. Upstream has been notified.

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Unfortunately, all of this comes down to the forced LTO. Disabling this in d/rules, per upstream, fixes the problem. He had a few more notes as well. It seems as though the Debian package is doing some unnecessary gymnastics, so this is a decent divergence.

diff --git a/debian/rules b/debian/rules
index a36f71d..6f12983 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,8 +1,8 @@
 #!/usr/bin/make -f

 # Let's try to cut down noisy symbols to the official API
-export DEB_CFLAGS_MAINT_APPEND = -fvisibility=hidden
-export DEB_CXXFLAGS_MAINT_APPEND = -fvisibility=hidden
+export DEB_CFLAGS_MAINT_APPEND = -fvisibility=hidden -fno-lto
+export DEB_CXXFLAGS_MAINT_APPEND = -fvisibility=hidden -fno-lto

 -include /usr/share/cdbs/1/rules/upstream-tarball.mk
 -include /usr/share/cdbs/1/rules/utils.mk

Changed in jackd2 (Ubuntu):
status: Triaged → In Progress
Changed in jackd2 (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jackd2 - 1.9.19~dfsg~ubuntu-0ubuntu2

---------------
jackd2 (1.9.19~dfsg~ubuntu-0ubuntu2) impish; urgency=medium

  * Remove LTO in build (LP: #1937325)
  * Add new internal zalsa client

 -- Erich Eickmeyer <email address hidden> Sun, 01 Aug 2021 15:16:22 +0000

Changed in jackd2 (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.