Subnostr

hmmm, looks like the detach persistent device bug is still persistent in 4.2

go to

/var/lib/qubes/qubes.xml

set mic device to null

save and reboot

all good?

*in dom0 ofc

Reply to this note

Please Login to reply.

Discussion

nostr:npub16v82nr4xt62nlydtj0mtxr49r6enc5r0sl2f7cq2zwdw7q92j5gs8meqha

4.2 introduced pipewire, but it's not officially supported in dom0

https://github.com/qubesos/qubes-issues/issues/6358#issuecomment-1712130215

some have reported a temporary fix

https://forum.qubes-os.org/t/4-2-sound-issue-and-temporary-fix/23095

but check this out before you go removing pipewire

https://forum.qubes-os.org/t/v4-2-pipewire-installation/19140

unfortunately i'm super busy atm and can't speak to your specific issue/hardware, but check this out as well

https://forum.qubes-os.org/t/qubes-4-2-audio-issues-need-to-reset-audio-output-for-each-new-qube-audio-use/19921/2

lmk how you go

I found the docs on how Qubes gets audio from and to VMs. https://www.qubes-os.org/doc/audio-virtualization/ and I have a pacat-simple-vchan process running (in dom0) for each vm, I have the UNIX sockets in dom0 as well, so everything looks reasonable there. In the VMs, I can see pulseaudio running, and audio played in a VM comes out the speakers, so audio transmission seems to be working fine in that direction...

I've given up for now and am using my Acusis Echo-Cancelling Microphone Array, which is a USB device that passes through just fine (just like all my other USB devices).

thx for the update. now i get your setup. glad you've got a fallback mic that works as it should. what was the one that was giving you trouble?