My goal: update Debian 13 via the Qubes OS update tool.
My problem: getting a failed to fetch for every single package in every single Debian Qube. When trying to update Debian the update tool freezes too. This only happens when updating Debian.
What I tried to do before asking for help:
Installing a new Debian template - doesn’t work.
Updating via dom0 - doesn’t work.
Updating via sudo apt update & upgrade in the Debian template - works but isn’t secure.
I reinstalled the template twice. The second time it worked and I got the update. I deleted the template for the old Debian Qubes and cloned from the updated template. But what’s weird is that the whole update application actually freezes too. Another user had the same. Maybe it’s just a bug.
Hello, not certain this is the same issue, but my installation gui updating broke recently (the 14th or 15th) as well for templates of both fedora and debian. Basically for TemplateVMs. The errors pointed to updateProxy and possibly DNS resolution.
My update resolution was pointed to by another user which deserves the resolution credit but sorry didn’t recall her name but you can search the forum for it, but her solution was related if I recall correctly to a discrepancy between the default net qube and the default update proxy setting in the global settings and the 90-default.policy.
This is located in dom0: /etc/qubes/policy.d/90-default.policy rule which has a line item default rule for updating all TemplateVMs which pointed to sys-net. I had my global setting of default netVM as sys-firewall as well and as being the same for the update proxy. Interestingly this has worked without issue set using sys-firewall for a long time so not certain why it suddenly had issues.
Anyways, in dom0 you can check qvm-features sys-net and verify if it lists “service.qubes-updates-proxy 1”. Mine had this parameter also set in qvm-features sys-firewall, probably via the gui setting I had, so I removed it since I had changed it to sys-net in global config to match the default net qube and then the updates were again working and have been since. . Like I said this may or may not be the same issue but the timing is very coincidental. Lastly, make sure your DNS is resolving correctly.
. Like I said this may or may not be the same issue but the timing is very coincidental. Lastly, make sure your DNS is resolving correctly.