Package: pipewire-pulse
Version: 0.3.39-3
Severity: normal
Dear Maintainer,
after the migration of pipewire 0.3.39 to testing I had to find a way to
have
back pulseaudio network transparency; after some searches on the web I found
that the pactl load-module command should still work with selected
modules [1],
and the modules I need appear supported. If it worked I just had to
figure out
how to load those modules automatically at each session.
The command
pactl load-module module-native-protocol-tcp
indeed worked, and I could verify the TCP port 4713 was open; then I
tried the
command
pactl load-module module-zeroconf-publish
but it errored out with the message "Failure: No such entity".
I'm now stuck wondering whether I missed something (there's not much on
the web
about Pipewire, even less about its network transparency) or it's a pipewire
bug, so please accept my excuses in case it's my fault...
Thanks
[1]
https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Migrate-PulseAudio#modules-1
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-proposed-updates
APT policy: (990, 'testing-proposed-updates'), (990, 'testing'), (500,
'stable-security'), (500, 'proposed-updates'), (500,
'oldstable-proposed-updates'), (500, 'unstable'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.14.15-xanmod1 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pipewire-pulse depends on:
ii init-system-helpers 1.60
ii libc6 2.32-4
ii libpipewire-0.3-0 0.3.39-3
ii pipewire 0.3.39-3
pipewire-pulse recommends no packages.
pipewire-pulse suggests no packages.