Bug 1972963 - audacity: no jack host listed via pipewire
Summary: audacity: no jack host listed via pipewire
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: audacity
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ian McInerney
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-17 01:26 UTC by space88man
Modified: 2021-06-22 02:25 UTC (History)
6 users (show)

Fixed In Version: audacity-3.0.2-3.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-22 01:01:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description space88man 2021-06-17 01:26:24 UTC
Description of problem:
On Fedora 34, audacity does not list Jack as available Host even though
pipewire-jack-audio-connection-kit is installed


Version-Release number of selected component (if applicable):
audacity-3.0.2-2.fc34.x86_64
portaudio-19-34.fc34.x86_64
pipewire-jack-audio-connection-kit-0.3.30-2.fc34.x86_64



How reproducible:
Always

Steps to Reproduce:
1. Install audacity(which pulls in portaudio), pipewire-jack-audio-connection-kit
2. Start Audacity
3. Edit -> Preferences -> Devices -> Host

Actual results:
Only ALSA is listed


Expected results:
Both ALSA and JACK listed


Additional info:
portaudio is picking up the correct Jack libraries
$ ldd /usr/lib64/libportaudio.so.2
	linux-vdso.so.1 (0x00007ffd6ebe8000)
	librt.so.1 => /lib64/librt.so.1 (0x00007fa8db705000)
	libasound.so.2 => /lib64/libasound.so.2 (0x00007fa8db5f8000)
	libjack.so.0 => /usr/lib64/pipewire-0.3/jack/libjack.so.0 (0x00007fa8db5c7000)
	libm.so.6 => /lib64/libm.so.6 (0x00007fa8db483000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa8db462000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fa8db447000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fa8db276000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007fa8db26f000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fa8db75e000)
	libpipewire-0.3.so.0 => /lib64/libpipewire-0.3.so.0 (0x00007fa8db1b0000)

Comment 1 space88man 2021-06-17 01:28:04 UTC
In separate testing: Reaper(commercial software, uses Jack directly) does indeed see Jack via pipewire.

Comment 2 space88man 2021-06-18 00:00:53 UTC
On my system, portaudio alone does detect JACK:

---snip---
// testpa.c
// gcc -o testpa testpa.c `pkg-config portaudio-2.0 --libs`

#include <portaudio.h>
#include <stdio.h>

int main(int argc, char** argv) {
	int i;
	PaHostApiIndex count;
	const PaHostApiInfo *phost;

	Pa_Initialize();


	count = Pa_GetHostApiCount();

	printf("count = %d\n", count);

	for (i = 0; i < count; i++) {

		phost = Pa_GetHostApiInfo(i);
		printf("index=%d name=%s deviceCount=%d\n", i, phost->name, phost->deviceCount);
     	}
}
---snip---

Output:
./testpa
count = 3
index=0 name=ALSA deviceCount=12
index=1 name=OSS deviceCount=0
index=2 name=JACK Audio Connection Kit deviceCount=11

Comment 3 Fedora Update System 2021-06-18 01:04:11 UTC
FEDORA-2021-1a043ee3d2 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-1a043ee3d2

Comment 4 Fedora Update System 2021-06-19 01:10:32 UTC
FEDORA-2021-1a043ee3d2 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-1a043ee3d2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1a043ee3d2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-06-22 01:01:37 UTC
FEDORA-2021-1a043ee3d2 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 space88man 2021-06-22 02:25:58 UTC
I would like to express my appreciation to the Fedora maintainer(s) of this package for the swift turnaround.


Note You need to log in before you can comment on or make changes to this bug.