Dom0 update error 'Another instance of qubes-dom0-update is already running!'

[kurt]

The latest 3 Dom0 updates failed. There is no obvious reason why this started.

The update process itself seems to complete without errors, but after all is finished this message occurs:

Complete!
Switching from Pulseaudio to PipeWire
Using sys-firewall as UpdateVM for Dom0
Downloading packages. This may take a while...
Another instance of qubes-dom0-update is already running!

Apparently all is still fine after this error, the system seems to be updated after all, booting is still OK, VM’s are all fine, just this curious error message concluding each Dom0 update.

Any suggestions on what is happening and how to proceed?

[apparatus]

It seems that it’s trying to switch from pulseaudio to pipewire automatically but it’s failing because of this bug:

Terrible audio quality after suspend, switching to Pipewire in dom0 does not work

PR Submitted Since copy/pasting patches to dom0 is a little bit hard, it might easier for you to do the patch manually. I submitted a smaller patch and you could apply it easily. Open the qubes-dom0-update script in dom0 with your favourite text editor (vim, nano, …) as root: sudo vim /usr/bin/qubes-dom0-update Go to line ~203 which should look like this (it might be few lines before or after line 203 in your machine): if [[ ${?} -ne 0 ]]; then …

You can manually fix the /usr/bin/qubes-dom0-update file in dom0 as suggested in the link or wait for it to be updated later.

[kurt]

Thanks Apparatus.

The bug reports are marked as solved, presumably it takes some time to move the fixes to stable. I’ll wait for these though, since I’m quite hesitant to edit Qubes scripts myself.

[kurt]

Is this really a known bug which is going to be fixed? The last two Dom0 updates failed again because of the same reason.

[apparatus]

It’s fixed but the new qubes-core-dom0-linux package containing the fix is not yet available.