VirtualBox

Ticket #19527 (new defect)

Opened 7 months ago

Last modified 3 months ago

The guest OS has access to the host microphone despite the "Enable Audio Input" setting being disabled.

Reported by: eqkb Owned by:
Component: audio Version: VirtualBox 6.1.6
Keywords: audio input microphone disable setting Cc:
Guest type: all Host type: all

Description

The guest OS has access to the host microphone despite the "Enable Audio Input" setting being disabled.

My host OS is Ubuntu 18.04 Host Audio Driver: PulseAudio Audio Controller: ICH AC97 VirtualBox 6.1.6

For the guest OS I have tested several Linux guests, I have not tested non-linux guests.

Steps to reproduce this bug:

  1. Create a new VM using an Ubuntu host and a Linux guest. (I don't know if this bug effects other hosts)
  2. Open the settings for the VM, click the audio tab and uncheck the "Enable Audio Input" setting.
  3. Start the VM.
  4. Use some application inside the VM to record audio or just look at the microphones sound levels from the guest OS's audio input settings.

Change History

comment:1 Changed 7 months ago by eqkb

This bug is also present when the host OS is Ubuntu 20.04.

comment:2 Changed 7 months ago by Pedro.VBox

This bug is also present when the host OS is Win10 x64 1909
It seems the "enabledIn" property won't get written to the *.vbox file when set to "false"

comment:3 Changed 6 months ago by TianGui

I also have this problem,but I use the vbox 5.2.36,the microphone icon flashes several times during virtual machine startup,and it won't disappear after the virtual machine starts...

Last edited 6 months ago by TianGui (previous) (diff)

comment:4 in reply to: ↑ description Changed 5 months ago by Abate Bus

I have the same problem since VirtualBox was updated to version 6.1.6_Ubuntu r137129. My host is Ubuntu 20.04. This bug is present in different guests (Windows10 and Ubuntu 20.04).

There's a solution?

Thanks

Last edited 5 months ago by Abate Bus (previous) (diff)

comment:5 Changed 3 months ago by aeichner

Could anyone please upload a full VBox.log at least? It provides valuable information for us when we try to reproduce the issue.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use