Hi!
Following the instructions how to remove obsolete templates, I have a
problem with both old whonix templates. The problem goes like this:
[master@dom0 ~]$ rpm -qa qubes-template-\*
qubes-template-debian-10-4.0.1-201912251612.noarch
qubes-template-whonix-ws-15-4.0.1-201910102356.noarch
On 11/16/21 11:38 PM, lik...@gmx.de wrote:
Hi!
I'd like to ask for recommendations for headset for video conferencing. It has
been said that my bluetooth headset with slack or microsoft teams do have much
worse audio quality with qubes than with windows.
The issue with modern bluetooth
On 11/15/21 11:35 AM, Peter Palensky wrote:
I use a video VM for MS Teams, Zoom, etc. and dom0 top shows >10% cpu
load for pulseaudio and pacat-simple-vchan (associated with that video VM).
Is that normal? It drains my battery (Dell XPS13, kernel 5.4.88-1, Qubes
4.0) really quickly.
Even
On November 20, 2021 8:46:58 PM UTC, 'awokd' via qubes-users
wrote:
>Viktor Ransmayr:
>> System clock synchronized: no
>>NTP service: inactive
>
>Any idea why this isn't running? If your hardware clock is close enough to the
>right time, it might not matter, but
Viktor Ransmayr:
System clock synchronized: no
NTP service: inactive
Any idea why this isn't running? If your hardware clock is close enough
to the right time, it might not matter, but can't be helping things.
It's showing as synchronized & active on my sys-net. I'm
Hello awokd,
awokd schrieb am Samstag, 20. November 2021 um 17:47:44 UTC+1:
> Viktor Ransmayr:
>
> > I don't want to adjust the time for the two Whonix templates manually to
> > the (wrong?) CET values, whenever an update is necessary.
> >
> > I don't think I had this issue with Whonix 15 &
Viktor Ransmayr:
I don't want to adjust the time for the two Whonix templates manually to
the (wrong?) CET values, whenever an update is necessary.
I don't think I had this issue with Whonix 15 & believe it only started
with Whonix 16.
Do you have any ideas or suggestions?
Check dom0's
pepito:
Note: I prefer not to run Android platform tools in sys-usb for the sake of
security/isolation.
This, or assigning a USB controller directly to your Android AppVM, is
the only way I've been able to get it to work.
--
- don't top post
Mailing list etiquette:
- trim quoted reply to
