Your message dated Wed, 30 Sep 2026 13:59:49 +0200
with message-id <[email protected]>
and subject line Re: Bug#1133171: pipewire 1.6.3-1 cannot load external plugin
has caused the Debian Bug report #1133171,
regarding pipewire 1.6.3-1 cannot load external plugin
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1133171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1133171
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pipewire
Version: 1.6.3-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
Starting with pipewire 1.6.3-1, external plugins fail to load. There are no
relevant errors or warnings in journalctl, nor in the pipewire or wireplumber
logs when started with PIPEWIRE_DEBUG=D and WIREPLUMBER_DEBUG=D.
After downgrading pipewire to 1.6.2-1 and rebooting (simply restarting the
pipewire/wireplumber services is not sufficient), the issue disappears and the
plugin loads correctly.
The affected plugin is DeepFilterNet:
https://github.com/Rikorose/DeepFilterNet
Please let me know if you need any additional information, logs, or testing.
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.19.11+deb14-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pipewire depends on:
ii libpipewire-0.3-modules 1.6.3-1
ii pipewire-bin 1.6.3-1
ii systemd [systemd-sysusers] 260.1-1
pipewire recommends no packages.
pipewire suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.6.6-1
On 23/04/2026 11:43, KeyofBlueS wrote:
As mentioned earlier, the behavior still appears tied to the restriction
introduced in 1.6.3 regarding loading plugins from absolute paths
outside the search path. Plugins located in a user directory (e.g.
~/.ladspa) are still not picked up, while moving them to /usr/lib/
ladspa/ works as expected.
Since this behavior is intentional, it shouldn't be considered a bug.
That said, if you think it would make sense to allow this use case by
including a user plugin directory (e.g. ~/.ladspa or ~/.local/lib/
ladspa) in the search path, I'd be happy to test it. However, I would
stick with the upstream behavior, I shouldn't have opened this report in
the first place, and it should be closed as wontfix/invalid.
This should be fixed with pipewire 1.6.6:
- Relax LADSPA path loading. Absolute paths are allowed when loading
modules from a config file. They are now only blocked when loading
the pulse ladspa modules and filter-chains in nodes because those
can load ladspa plugins in other processes. (#5222)
Best regards,
Dylan
--- End Message ---
