[qubes-users] migration to pipewire not working (Qubes 4.2.3)

Hi,

I use sys-usb as audio VM,
[user@dom0 ~]$ qvm-prefs video audiovm
sys-usb

and everything works fine.

Now i want to migrate from pulseaudio to pipewire:
[root@deb12-template]$ apt install pipewire-qubes pipewire-audio pipewire wireplumber pipewire-alsa libspa-0.2-bluetooth

Now sound [still] plays nicely in sys-usb:

user@sys-usb:~$ pw-cat -p /usr/share/sounds/alsa/Front_Right.wav

and pavucontrol shows all hardware (also bluetooth headset etc.).

But the app VMs (such as ‘video’) are silent. pavucontrol ‘Control’ tab shows no cards (it should show qubes vchan sink and source), same with
user@video:~$ wpctl status

Audio
├─ Devices:

├─ Sinks:
│ * 36. Dummy Output [vol: 1.00]

├─ Sink endpoints:

├─ Sources:

├─ Source endpoints:

└─ Streams:

There are many pw nodes registered, only one (number 28) says qubes:
user@video:~$ pw-cli ls

id 27, type PipeWire:Interface:Factory/3
object.serial = “27”
module.id = “21”
factory.name = “endpoint-link”
factory.type.name = “PipeWire:Interface:EndpointLink”
factory.type.version = “0”
id 28, type PipeWire:Interface:Module/3
object.serial = “28”
module.name = “libpipewire-module-qubes”
id 29, type PipeWire:Interface:Node/3
object.serial = “29”
factory.id = “10”
priority.driver = “20000”
node.name = “Dummy-Driver”

id 36, type PipeWire:Interface:Node/3
object.serial = “36”
factory.id = “18”
client.id = “32”
node.description = “Dummy Output”
node.name = “auto_null”
media.class = “Audio/Sink”

What is missing? How can app VMs connect to my audio VM via pipewire?

1 Like