Pipewire 1.0.0 seems to randomly use either a sink or a source (not both) when using zeroconf
- PipeWire version (
pipewire --version
):
1.0.0 - ArchLinux (discover), updated from 0.3.79 to 1.0.0
0.3.65 - Raspbian (publish)
- Distribution and distribution version (
PRETTY_NAME
from/etc/os-release
):
Publishing from Raspbian, discovering from ArchLinux
- Desktop Environment:
KDE
- Kernel version (
uname -r
):
ArchLinux - 6.1.71-1-lts
Raspbian - 6.1.0-rpi6-rpi-v7
Description of Problem:
Before updating from 0.3.79 on ArchLinux to 1.0.0 both the sink and the source I'm publishing from a Raspberry PI showed up almost instantly as a source and sink.
After updating to 1.0.0 it seems to be somewhat random which one shows up, but never both. If I load and unload module-zeroconf-discover I either get the sink or the source showing up.
How Reproducible:
100% of the time.
Steps to Reproduce:
- Install Raspbian on a PI, connect a USB headset with headphones and mic
- Publish from the PI, Discover from ArchLInux
Actual Results:
Either the sink or the source shows up under ArchLinux using 1.0.0 when loading the zeroconf module.
Unloading and loading results in the same, either the sink or source shows up.
Expected Results:
Both sink and source to be available.
Additional Info (as attachments):
I ran pw-mon while doing this and I only see either the sink or source showing up, I never see both in the logs displayed.
My PC was off for a few months while moving, the last time I used zeroconf to remotely access a headset was sometime during September. After updating today from 0.3.79 to 1.0.0 I'm getting the odd behavior.