qubes-issues

qubes-issues copied to clipboard

How to file a helpful issue

Qubes OS release

4.2

Brief summary

Calling the GUI updater from the CLI with the --restart parameter doesn't force the restart of affected app qubes.

Steps to reproduce

1. qubes-update-gui --restart
2. Confirm that no qubes are restarted automatically
3. If any update failed, confirm that exit code is still zero

Expected behavior

Update-affected app qubes would restart automatically without any user interaction. Either that or appear pre-selected, just waiting for the user to click "next" (but not editable). After any failure, the exit code would be non-zero.

This is the same behavior as the CLI counterpart qubes-vm-update --restart in the sense that it does force the restart of app qubes. (although the restart does happen regardless of whether or not there were updates, but that's another issue https://github.com/QubesOS/qubes-issues/issues/9031).

Actual behavior

--restart option doesn't does not force the app qubes to be restarted.

Is this duplicate of #9024 ?

I don't think it is because here the problem is when calling it from the terminal and not necessarily just a problem with the UI itself.

Isnt this exacty the behavior you would expect to see given that --restart doesnt work in the GUI?

Not really. My point here is that the "restart" option doesn't get selected at all. So the app qubes don't even shut down by default much less restart. So it's an issue before #9024 even has a chance to manifest. Does this make sense?

Not being a user of the GUI I dont know how you would know this. But if you can see that the GUI launches without that option being selected, you are right, this is probably a separate issue. But the solution may be the same.

It may well be the same, but at least the symptoms are slightly different and so I'd argue it merits to different reports until that is cleared up.

I should also add that this particular Qubes 4.2 was installed from RC (maybe RC4) and updated until today. I recall some conversation about selecting qubes for restart these by default. If that's the case then that may obscure this diagnosis.

I have noticed that on my original screenshot the qubes were not selected, but on a new install they are. I believe that the system which I used to report was installed on an RC and so it might have the default option to restart qubes as disabled (whereas they are now enabled by default).

So I have edited the title and description to make this issue focus more on the enforcing restarts.

Update-affected app qubes would restart automatically without any user interaction. Either that or appear pre-selected, just waiting for the user to click "next" (but not editable).

(bold part is new) Edited the original post to make my request a bit clearer. I think --restart should force qubes to be restarted. Ideally started automatically.

I have split lack of non-zero exit codes into its own issue. Should have done so in the original report. Sorry about that https://github.com/QubesOS/qubes-issues/issues/9225.