Building on my personal theme of “Why does Qubes OS hate me specifically so much” I recieved the following error while updating Dom0 today:
Updating dom0
Error on updating dom0: Command '['sudo', 'qubesctl', '--dom0-only', '--no-color', 'pkg.upgrade', 'refresh=True']' returned non-zero exit status 1.
[ERROR ] Command 'systemd-run' failed with return code: 1
[ERROR ] stderr: Running scope as unit: run-rb426c1a2c062406987ac00afd070b37f.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--clean' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 1
[ERROR ] retcode: 1
Error running 'pkg.upgrade': Problem encountered upgrading packages. Additional info follows:
changes:
----------
result:
----------
pid:
8175
retcode:
1
stderr:
Running scope as unit: run-rb426c1a2c062406987ac00afd070b37f.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--clean' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 1
stdout:
I’d love to tell you specifically what update that was and assign some kind of version number to it, but I have no idea where to find that information, so the best I can tell you is it was definitely released this week, as I’m pretty punctual with dom0 updates.
Since the definition of insanity is doing the same thing over and over again and expecting a different result, and i’m rapidly getting there, I decided to try the Dom0 update again and… Success! … I think?
Updating dom0
local:
----------
kernel:
----------
new:
1000:5.15.103-1.qubes.fc32,1000:5.15.89-1.fc32.qubes,1000:5.15.94-1.qubes.fc32
old:
1000:5.15.81-1.fc32.qubes,1000:5.15.89-1.fc32.qubes,1000:5.15.94-1.qubes.fc32
kernel-devel:
----------
new:
1000:5.15.103-1.qubes.fc32,1000:5.15.89-1.fc32.qubes,1000:5.15.94-1.qubes.fc32
old:
1000:5.15.89-1.fc32.qubes,1000:5.15.94-1.qubes.fc32
kernel-modules:
----------
new:
1000:5.15.103-1.qubes.fc32,1000:5.15.89-1.fc32.qubes,1000:5.15.94-1.qubes.fc32
old:
1000:5.15.89-1.fc32.qubes,1000:5.15.94-1.qubes.fc32
kernel-qubes-vm:
----------
new:
1000:5.15.103-1.qubes.fc32,1000:5.15.89-1.fc32.qubes,1000:5.15.94-1.qubes.fc32
old:
1000:5.15.81-1.fc32.qubes,1000:5.15.89-1.fc32.qubes,1000:5.15.94-1.qubes.fc32
python3-qubesdb:
----------
new:
4.1.16-1.fc32
old:
4.1.15-1.fc32
qubes-db:
----------
new:
4.1.16-1.fc32
old:
4.1.15-1.fc32
qubes-db-dom0:
----------
new:
4.1.16-1.fc32
old:
4.1.15-1.fc32
qubes-db-libs:
----------
new:
4.1.16-1.fc32
old:
4.1.15-1.fc32
qubes-mgmt-salt-base:
----------
new:
4.1.5-1.fc32
old:
4.1.4-1.fc32
As you can see the update message just sort of abruptly stops, rather then ending with any kind of reassuring conclusion like i’m used to seeing from fedora updates. So i’m not 100% sure if attempt number 2 was a complete success or not. And I can’t remember if that’s normal. After all any subsequent updates just receive this:
Updating dom0
local:
----------
Which my stressed mind was sure wasn’t normal, but it’s actually a completely normal response to no updates being available.
Anyway, sorry for rambling. Basically I just want a second opinion on if my systems “probably ok” or not. It looks like the update went through the second time and the system rebooted fine, but this the first time a dom0 update has ever failed for me so i’d love some reassurance that I should just carry on like normal.