You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When starting virt-manager from a rootfull+init dbox, the USB audio devices are no more accessible from other apps, such as Chrome or Brave browsers (installed as flatpak).
Create a test VM with all the defaults (it doesn´t need to be started aftwerards)
Exit dbox and stop it:
exit
distrobox stop --root virt
Start a web app that requires sound (i.e. meet.google.com)
Open virt-manager (from the desktop icon if exported, or from the CLI inside the dbox)
RESULTS: the running app (i.e. meet.google.com) has no more access to sound devices.
Expected behavior
The sound devices should remain available to the running apps.
Logs
N/A and specific logs can be provided on-demand.
Desktop (please complete the following information):
Are you using podman, docker or lilipod? Podman
Which version or podman, docker or lilipod? 5.0.3
Which version of distrobox? 1.7.2.1
Which host distribution? Aeon
How did you install distrobox? installed by default
Additional context
I have a workaround: my audio devices are all USB, and if I remove the USB redirection from the VMs configuration, I don't have this issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
When starting virt-manager from a rootfull+init dbox, the USB audio devices are no more accessible from other apps, such as Chrome or Brave browsers (installed as flatpak).
To Reproduce
exit distrobox stop --root virt
RESULTS: the running app (i.e. meet.google.com) has no more access to sound devices.
Expected behavior
The sound devices should remain available to the running apps.
Logs
N/A and specific logs can be provided on-demand.
Desktop (please complete the following information):
Additional context
I have a workaround: my audio devices are all USB, and if I remove the USB redirection from the VMs configuration, I don't have this issue.
The text was updated successfully, but these errors were encountered: