So I'm having a really hard time assigning USB devices.
Here is what happens with the Yeti mic.
I am in QUBES 3.2
When I plug in the mic, it actually immediately shows up in the audio mixer,
under "capture devices".. I also see it in Pulse audio manager.
The question is then just how to
I have a Blue Mic Yeti and am trying to get it working with QUBES.
I tried attaching audio to a VM, but it didn't work.
I need a simple step-by-step guide for how to use a USB mic with QUBES.
The mic is plug-and-play, and requires no installation, both in Linux and in
Windows.
--
You
I am using QUBES 3.0
Fedora-21
When I install certain programs in the template VM for fedora, they do not show
up in the AppVMs, even after restarting each of the AppVMs.
I installed google-chrome-stable, and yet, it's not reflected in the AppVMs.
I have to re-install Chrome inside the actual
OK
Version: 4.4.3
Release: 11.fc20
So I am OK.
Does QUBES 3.0 come with the patched version though... Have the devs updated
the ISO so that it comes patched..?
Or am I patched because I did a dom0 update..?
Thanks
--
You received this message because you are subscribed to the Google
I have a question about the Xen sandbox escape from Oct 2015
https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-022-2015.txt
I am running Qubes 3.0.
Qubes 3.0 was released Oct 1 2015.
The Xen glitch was Oct 29 2015.
Does this mean that Qubes 3.0 does not come shipped with the
I installed the debian and whonix templates
But then, whenever I open VM Manager, I get the following error:
"Whoops. A critical error has occured. This is most likely a bug in Qubes
Manager.
libvirtError: internal error: client socket is closed at line 1268 of the file
libvirt.py"
Not