VM sigkill-at-will, d-bus broker service and qubesd fail to boot, attack disables Qubes Updater

[ghostsinthebaseband]

Connected to these attacks on Qubes Updater

Qubes Updater infinite lag (neverized) on Templates and associated issues

For some reason, any Standalone qube will not update with Qubes Updater strategy if any VPN applications are installed (Mullvad or Proton). So I removed them. Encrypted DNS should be sufficient unless they start blocking the news on the IP level in the US and the news site also blocks tor. VPN doesn’t provide any further layer of network security than encrypted DNS, wouldn’t you agree? But I wonder why updates can proceed through qube terminal but not through Qubes Updater which is supposed to …

Has anyone used the Ignite .onion repodata?