Bug 2263486

Summary:	pipewire: pipewire-jack-audio-connection-kit-libs provides libjack.so.0()(64bit) without installing it
Product:	[Fedora] Fedora	Reporter:	Florian Weimer <fweimer>
Component:	pipewire	Assignee:	Wim Taymans <wtaymans>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	42	CC:	brunovern.a, code, information, ngompa13, supersonic112+redhat, wtaymans
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-03-06 13:42:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Florian Weimer 2024-02-09 09:37:34 UTC

The file is only installed under /usr/lib64/pipewire-0.3/jack/libjack.so.0, which is not in the default library search path. This means that if pipewire-jack-audio-connection-kit-libs is installed for satisfying the libjack.so.0()(64bit) dependency, applications will not work.

Seen with pipewire-jack-audio-connection-kit-libs-1.0.3-1.fc40.x86_64 while trying to rebuild fmidi in local mock or in COPR.

Reproducible: Always

Comment 1 supersonic112+redhat 2024-07-05 19:31:37 UTC

Hi, I recently encountered a very similar problem - in my case, the lib64 path was available (through the string `/usr/lib64/pipewire-0.3/jack/` in the file `/etc/ld.so.conf.d/pipewire-jack-x86_64.conf`), but when I additionally installed the i686 version of the package, the file `/etc/ld.so.conf.d/pipewire-jack-i686.conf` was not created. http://src.fedoraproject.org/rpms/pipewire/blob/f40/f/pipewire.spec#_452 looks like it should create the file correctly for any architecture, though I'm unfortunately not yet deep enough into the RPM build system to analyze any deeper. I just double-checked on a second Fedora 40 system, the issue is reproducible.

The workaround in my case was to create the missing `/etc/ld.so.conf.d/pipewire-jack-i686.conf` file with the content `/usr/lib/pipewire-0.3/jack/` and to then run `ldconfig` with root privileges.

PS: if adding this potentially different issue here is undesired and should instead be filed as a separate bug, please tell me, this is my first finding of this kind.

Comment 2 Aoife Moloney 2025-02-26 12:57:50 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 3 Ben Beasley 2025-03-06 13:24:14 UTC

As the maintainer of the fmidi package, this just came to my attention because fmidi has started to FTBFS since pipewire-jack-audio-connection-kit-libs became part of the recursive dependency tree, http://koschei.fedoraproject.org/build/19802115.

Even if I work around the problem by adding

  export LDFLAGS="${LDFLAGS} $(pkg-config --libs jack)"

before %cmake in the fmidi spec file, this is still a problem at runtime. If I install fmidi-libs, fmidi-tools, and pipewire-jack-audio-connection-kit-libs together in a Rawhide mock chroot, this happens:

  # fmidi-play
  fmidi-play: error while loading shared libraries: libjack.so.0: cannot open shared object file: No such file or directory

This PR and the discussion therein seem to be related: http://src.fedoraproject.org/rpms/pipewire/pull-request/31

Comment 4 Neal Gompa 2025-03-06 13:42:57 UTC


*** This bug has been marked as a duplicate of bug 2345985 ***