[qubes-users] dnf remove lies to me (removing whonix-15 templates)

[Ulrich Windl]

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
qubes-template-whonix-gw-16-4.0.6-20210921.noarch
qubes-template-whonix-gw-15-4.0.1-201910102356.noarch
qubes-template-whonix-ws-16-4.0.6-20210921.noarch
[master@dom0 ~]$ sudo dnf remove qubes-template-whonix-ws-15
Dependencies resolved.

 Package Arch 
Version Repository Size


Removing:
 qubes-template-whonix-ws-15 noarch 
4.0.1-201910102356  @anaconda 2.1 G


Transaction Summary

Remove  1 Package

Installed size: 2.1 G
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
usage: qvm-template-postprocess [--verbose] [--quiet] [--help] [--really]
[--skip-start] [--keep-source]
{post-install,pre-remove} name dir
qvm-template-postprocess: error: No Qube with this name exists
error: %preun(qubes-template-whonix-ws-15-4.0.1-201910102356.noarch) 
scriptlet failed, exit status 2

Error in PREUN scriptlet in rpm package qubes-template-whonix-ws-15
Error in PREUN scriptlet in rpm package qubes-template-whonix-ws-15
qubes-template-whonix-ws-15-4.0.1-201910102356.noarch was supposed to be 
removed but is not!
  Verifying   : qubes-template-whonix-ws-15-4.0.1-201910102356.noarch 
1/1


Removed:
  qubes-template-whonix-ws-15.noarch 4.0.1-201910102356 



Complete!
[master@dom0 ~]$

Specifically: Even when saying "Removed: ...", the package was *not* 
removed.


Same for the "whonix-gw-15" package.

Regards,
Ulrich

--
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 it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/60609ffd-a0e6-f4c7-e94a-bd21c77c674a%40rz.uni-regensburg.de.

Re: [EXT] [qubes-users] headset recommendation for video conferencing with good audio quality

[Ulrich Windl]

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 headsets is typically not quality but 
latency. The good old cable-type headset is probably still the best.




Any recommendations from the community? Bonus for bluetooth headsets.

Thanks!



--
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 it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0f91d60f-97fb-80fe-cc0c-c4438d06e550%40rz.uni-regensburg.de.

Re: [EXT] [qubes-users] video conferencing: high dom0 cpu load by pulseaudio

[Ulrich Windl]

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 outside of Qubes-OS I feel video conferencing software is highly 
inefficient. When I had a Webex session on my old AMD Phenom 2 Quad 
Core, the CPU fan got louder and louder...




--
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 it, send 
an email to qubes-users+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c881090e-18a9-4618-86ff-8ec310f6021fn%40googlegroups.com 
.


--
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 it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3e325960-ad37-83f9-e3b8-ee52218bf60e%40rz.uni-regensburg.de.

Re: [qubes-users] Re: Qubes Update does not work for Whonix 16 templates ...

[Insurgo Technologies Libres / Open Technologies]

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 can't be helping things. It's showing as 
>synchronized & active on my sys-net. I'm running 4.1, but pretty sure it 
>showed the same on 4.0.
>

Dom0 (timedatctl) doesn't know dom0 has time synchronization, since its 
provided per sys-net by default which is provided as a qubesos service.

You can force time sync once sys-net is network connected by doing the 
following from dom0 Terminal Emulator:
sudo qvm-sync-clock 

Now, sys-net and dom0 are time synced.
Time to restart all qubes:
qvm-shutdown --all --wait

Then all new qubes launched will have dom0 new synced time.

Hope that helps.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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 it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7355104B-B880-4952-82B3-7EE3CA20B0AD%40gmail.com.

Re: [qubes-users] Re: Qubes Update does not work for Whonix 16 templates ...

['awokd' via qubes-users]

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 running 4.1, 
but pretty sure it showed the same on 4.0.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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 it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0ea29184-310e-ed79-e6cb-533763ca88a2%40danwin1210.me.

Re: [qubes-users] Re: Qubes Update does not work for Whonix 16 templates ...

[Viktor Ransmayr]

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 & believe it only started 
> > with Whonix 16. 
> > 
> > Do you have any ideas or suggestions? 
>
> Check dom0's clockvm with "qubes-prefs" in a terminal. It's probably 
> sys-net. 


Yes it is. Here are the complete preferences:

[vr@dom0 ~]$ qubes-prefs
check_updates_vm  D  True
clockvm   -  sys-net
default_dispvm-  fedora-34-dvm
default_kernel-  5.4.143-1.fc25
default_netvm -  sys-firewall
default_pool  D  lvm
default_pool_kernel   -  linux-kernel
default_pool_private  D  lvm
default_pool_root D  lvm
default_pool_volatile D  lvm
default_qrexec_timeoutD  60
default_shutdown_timeout  D  60
default_template  -  fedora-34
management_dispvm -  default-mgmt-dvm
stats_intervalD  3
updatevm  -  sys-firewall
[vr@dom0 ~]$ 

Confirm the timezone and time are set correctly inside sys-net 
> (or your clockvm if different). 


Here are the results of 'timedatectl':

[user@sys-net ~]$ timedatectl
   Local time: Sat 2021-11-20 18:34:11 CET
   Universal time: Sat 2021-11-20 17:34:11 UTC
 RTC time: Sat 2021-11-20 17:34:11
Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: no
  NTP service: inactive
  RTC in local TZ: no
[user@sys-net ~]$ 

If that doesn't do it, and you can 
> afford it, might try a fresh install of 4.1rc2, and making sure to set 
> the correct timezone on install. Hard to know which time zone setting is 
> incorrect. 
>

A check with / upgrade to  4.1rc2 is not an option for me. - At least not 
in November ...

With kind regards,

Viktor

-- 
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 it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b929b00b-c159-4c55-a60b-4f13f239eaffn%40googlegroups.com.

Re: [qubes-users] Re: Qubes Update does not work for Whonix 16 templates ...

['awokd' via qubes-users]

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 clockvm with "qubes-prefs" in a terminal. It's probably 
sys-net. Confirm the timezone and time are set correctly inside sys-net 
(or your clockvm if different). If that doesn't do it, and you can 
afford it, might try a fresh install of 4.1rc2, and making sure to set 
the correct timezone on install. Hard to know which time zone setting is 
incorrect.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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 it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/de6c568f-a94a-2924-ce96-be2559599896%40danwin1210.me.

Re: [qubes-users] Android USB debugging

['awokd' via qubes-users]

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 only relevant portions
- when possible, copy and paste text instead of screenshots

--
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 it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/593f88fa-45e5-1aeb-0f12-c23c24d68ce2%40danwin1210.me.