I ask because I updated dom0 using the Qubes Updater (due to issues with the CLI command) so I have no idea what has been updated or even whether something has been updated (with the ‘details’ box open). All I see is a tick next to dom0 in the updater when all is finished and an uninformative report in the ‘details’ box.
After I restarted my PC, my Wireguard connections no longer work. I’ve tried a whole lot of different fixes, but none work. I even deleted and re-created that Qube. I can confirm it’s not an issue on the provider’s end, and I made no changes before the routine update, so I have to suspect that dom0 was updated with something before the restart, and whatever it was broke my Wireguard connections.
Is there a way to make the Qubes Updater more verbose? It really should at least inform users what was updated and whether there was an update. Even a “No update is available” would be nice. This is one of the reasons I used
qubes-dom0-update and not the Qubes Updater, until this bug came to light and a huge warning sign had to be slapped on the documentation warning people away from the CLI version.
Am I the only one feeling dom0 updates aren’t in a good place right now? As an added bonus, I get a whole bunch of errors when I try to update my templates via the updater.