The question probably comes down to: Does disabling the microphone make
it invisible or just dysfunctional? Have you researched that?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from
On Sat, 27 Apr 2024 14:30:00 + ales...@magenta.de wrote:
> I still need to know what is best way for undervolt.py to run.
There is no best way to run potentially dangerous software.
> For best way I mean for security and without making more performance
> hit like maybe running a new qube.
>
one bug: man page for qube-dom0-update refers to yum instead of dnf.
another bug: system went to sleep / suspend when it was in the middle of
downloading updates with Qubes Update command. Not good. I have to
myself disable suspend in settings until it is finished.
last bug: many of my qubes
ales...@magenta.de:
What is the safest way to use undervolt script in Qubes?
https://github.com/georgewhewell/undervolt.git
This is running on Python. Is it better to use new service qube for this
or can I run it in dom0/sys-net/sys-firewall?
I still need to know what is best way for
I have just seen that there is a microphone device listed in the devices
menu.
I have already disabled built in microphone with firmware setting and
this doesn't shown in Ubuntu but is shown in Qubes. This laptop doesn't
have another microphone device.
How can Qubes see this device?
--
You
'unman' via qubes-users:
Have you assigned the device to sys-net in the "devices" tab of sys-net
settings.
I didn't know I had to do this. Now is fixed, thank you.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group
