RTKit error messages is a known bug [1], pipewire services are started before rtkit service thus pipewire fails to received the requested priority for realtime stuff. I confirm this is not related
to the "no device shown" symptom.
This "no device shown" symptom is due to a race condition between pipewire-pulse and wireplumber services [2]. The pipewire-pulse service is ready before wireplumber, thus wireplumber doesn't report any available device to pipewire-pulse.
I proposed a debdiff in [3] to avoid this issue. I attach the debdiff here again.
RTKit error messages is a known bug [1], pipewire services are started before rtkit service thus pipewire fails to received the requested priority for realtime stuff. I confirm this is not related
to the "no device shown" symptom.
This "no device shown" symptom is due to a race condition between pipewire-pulse and wireplumber services [2]. The pipewire-pulse service is ready before wireplumber, thus wireplumber doesn't report any available device to pipewire-pulse.
I proposed a debdiff in [3] to avoid this issue. I attach the debdiff here again.
[1] https:/ /bugs.debian. org/995357 /bugs.debian. org/1020575 /bugs.launchpad .net/ubuntu/ +source/ pipewire/ +bug/1990313/ comments/ 5
[2] https:/
[3] https:/