Qubes Updater GUI and CLI issues

User Support
1

I checked out this other thread (Error 126 while Updating the OS from Terminal) because qubes-dom0-update was throwing retcode 126 as well but it is likely unrelated; IMHO the other issue is incorrectly fixed and no valid solutions were recommended.

output from :

sudo qubesctl --show-output state.sls update.qubes-dom0

local:
----------
ID: /etc/yum.repos.d/qubes-dom0.repo
Function: file.replace
Result: True
Comment: No changes needed to be made
Started: 15:47:36.545518
Duration: 12.77 ms
Changes:
----------
ID: /etc/yum.repos.d/qubes-templates.repo
Function: file.replace
Result: True
Comment: No changes needed to be made
Started: 15:47:36.559206
Duration: 2.576 ms
Changes:
----------
ID: update
Function: cmd.script
Result: True
Comment: Cache cleaned
Started: 15:47:36.562847
Duration: 13538.462 ms
Changes:
----------
ID: update
Function: pkg.uptodate
Result: False
Comment: Problem encountered upgrading packages. Additional info follows:

          result:
----------
              pid:
                  85251
              retcode:
                  126
              stderr:
                  Running scope as unit: run-r4dc538318f154a21a1a0e186dff04260.scope
                  Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time...
                  Unable to detect release version (use '--releasever' to specify release version)
                  Request refused
                  '/usr/lib/qubes/qrexec-client-vm dom0 qubes.ReceiveUpdates /usr/lib/qubes/qfile-agent /var/lib/qubes/dom0-updates/packages/*.rpm' failed with exit code 126!
              stdout:
 Started: 15:47:52.303487
Duration: 241014.943 ms
 Changes:   

Summary for local
------------
Succeeded: 3
Failed:    1
------------
Total states run:     4
Total run time: 254.569 s

etc release files

/etc/qubes-release — content — Qubes release 4.2.2 (R4.2)

/etc/redhat-release — content — Qubes release 4.2.2 (R4.2)

/etc/fedora-release — content — Qubes release 4.2.2 (R4.2)

not sure of the issue or how to fix it because my release files are intact and correct, maybe I am meant to be using the fedora release num instead (37?).

as of the moment I cannot update my machine through the qubes GUI or CLI regarding dom0 though updating VMs individually through CLI from within vm-templates seems to work while updating the same vms from the GUI does not work (both should be using tor routing); the GUI results in Errors from fetching index files which are clearly reachable through apt-get over tor, and dom0 updates over and over while appearing to be successful as indicated by the check mark next to the update.

excuse my formatting

2

Welcome!

Have you looked at sys-net? If not, here is the guide:

  1. Go to sys-net terminal
  2. In sys-net terminal, type this following:
sudo systemctl status qubes-updates-proxy
  1. If that says failed, then type this:
sudo systemctl restart qubes-updates-proxy
  1. Always go to the qubes settings of sys-net at “Services” tab.
  2. Select “qubes-updates-proxy” and click ‘add’
  3. Click OK to affirm fast
  4. Reboot
3

qubes-updates-proxy is active by default for me. Following all of the steps in your post has left me at the same error message. Thank you for trying to help me.

4

reinstalling the qubes-release package has had no effect on the issue… I am completely lost as this seemed like the correct solution to the --releasever err msg; I was looking through the patch-dnf-yum-config script in /usr/lib/qubes and assumed that the final line “distroverpkg = qubes-release” was the issue. I am going to manually update the qubes I use and move on with a fresh OS install, i’ve been wanting to rip out xfce but that means ill have to install twice because qubes builder wouldnt work in my current env.