Public bug reported:
On Linux Mint 22.2 (based on Ubuntu 24.04 LTS Noble), PipeWire version
1.0.5‑1ubuntu3.1 fails to start correctly because it looks for modules
in /usr/lib/pipewire-0.3/. However, the package actually installs them
in /usr/lib/x86_64-linux-gnu/pipewire-0.3/.
This mismatch causes the following issues:
pipewire.service crashes with “could not load mandatory module”
errors.
pipewire-pulse.service starts but fails to create
/run/user/1000/pulse/native.
pactl info returns Connection refused until a manual workaround is
applied.
Steps to reproduce:
Install PipeWire from Ubuntu Noble repositories.
Check /usr/lib/pipewire-0.3/ → directory is missing.
Check /usr/lib/x86_64-linux-gnu/pipewire-0.3/ → modules are present.
Start pipewire.service → fails to load modules.
Workaround: Creating a symlink from /usr/lib/x86_64-linux-
gnu/pipewire-0.3 to /usr/lib/pipewire-0.3 resolves the issue. After
reloading systemd and restarting PipeWire services, PipeWire starts
correctly, pipewire-pulse creates the native socket, and pactl info
connects successfully.
System info:
Release: Linux Mint 22.2 (based on Ubuntu 24.04 LTS Noble)
Package version: pipewire 1.0.5‑1ubuntu3.1 (from noble‑updates/main)
Kernel: 6.8.0‑90‑generic
Logs: Dec 11 18:42:10 Rick-PC systemd[1388]: Started
pipewire.service - PipeWire Multimedia Service. Dec 11 18:42:10 Rick-PC
pipewire[1403]: mod.jackdbus-detect: Failed to receive jackdbus reply:
org.freedesktop.D>
Additional context on Multiarch library paths: Ubuntu and its
derivatives (including Linux Mint) use a Multiarch directory scheme to
support multiple CPU architectures side‑by‑side. Instead of installing
libraries directly under /usr/lib/, packages place them in
architecture‑specific subdirectories such as /usr/lib/x86_64-linux-gnu/
for 64‑bit systems.
In this case, the PipeWire package installs its modules under
/usr/lib/x86_64-linux-gnu/pipewire-0.3/, but the service files and
configuration still expect them in /usr/lib/pipewire-0.3/. This mismatch
between the Multiarch path and the expected upstream path is the root
cause of the failure.
Correcting the service files to reference the Multiarch location, or
shipping a symlink by default, would resolve the issue without requiring
manual intervention from users.
Impact: This packaging mismatch prevents PipeWire from functioning
out‑of‑the‑box on affected systems. Fixing the service files or shipping
the symlink by default would prevent users from having to manually patch
their installations
** Affects: pipewire (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2135062
Title:
PipeWire fails to start: modules installed in /usr/lib/x86_64-linux-
gnu/pipewire-0.3/ but service expects /usr/lib/pipewire-0.3/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2135062/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
