Qube with no microphone attached appears to have a broken sound card #7656
Labels
affects-4.1
This issue affects Qubes OS 4.1.
C: audio
diagnosed
Technical diagnosis has been performed (see issue comments).
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
How to file a helpful issue
Qubes OS release
R4.1
Brief summary
If a qube does not have a microphone assigned to it, it will never receive input on the recording vchan. With the current implementation of the Linux PulseAudio agent, this causes applications to think there is a microphone present, but that microphone never produces any audio samples and so appears to be broken. The result of this is application-dependent: gnome-sound-recorder pauses audio recording, while Discord refuses to use it and requires me to disconnect and reconnect from the call.
Steps to reproduce
Have an application try to record audio in a qube with no microphone attached to it.
Expected behavior
From the application’s perspective, the qube either has no microphone at all attached, or it appears to have a microphone that always records silence. If the first option is chosen, attaching and detaching the microphone should act as if a USB microphone was plugged and unplugged, respectively.
Actual behavior
To the application, the qube appears to have a microphone that is broken.
The text was updated successfully, but these errors were encountered: