Arch Linux

Description:

The latest upstream version of pipewire (0.3.71) includes a new module called jackdbus-detect which allows pipewire to run as a JACK client and lets you use the native jack instead of pipewire-jack (https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.71#highlights).

I followed the docs to set this up (https://docs.pipewire.org/page_module_jackdbus_detect.html) but pipewire wouldn't start and complained that this module didn't exist.
The docs include a spelling mistake with the module name but even after correcting this it didn't fix the issue.

In fact that module (libpipewire-module-jackdbus-detect.so) and the other required jack-tunnel module (libpipewire-module-jack-tunnel.so) are not available with the latest packaged version of pipewire.

Steps to reproduce:

1. Install pipewire, jack2 and jack2dbus
2. Copy `/usr/share/pipewire/pipewire.conf` to `~/.config/pipewire/pipewire.conf`
3. Add { name = libpipewire-module-jackdbus-detect } to `context.modules` in `~/.config/pipewire/pipewire.conf`
4. Pipewire fails to start with "file not found" error


Possible fix:

I noticed that this module is only built when jack is available based on these lines from the upstream build scripts:

https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/dfeacaafdd4dd63f6b7cd659d46de19cb2228b70/src/modules/meson.build#L163-184

I also noticed that there is a flag passed to the pipewire build in the PKGBUILD disabling jack:

https://gitlab.archlinux.org/archlinux/packaging/packages/pipewire/-/blob/355bad58ec7e1f5bc9b7f46dfc1543badf17d034/PKGBUILD#L89

Removing this line and adding jack2 as a makedepend fixes the issue on my machine - but I'm not sure if there are any other implications with doing this.
For example I don't think it makes sense to add this to the pipewire-jack module but naturally the pipewire module shouldn't depend on jack.

Perhaps there should be a new pipewire-jackdbus-detect module that includes this?