While waiting for some updates to come up to test if I understand your previous post and to post outputs here (and I guess I understand and that is exactly why I posted my question as an addition to he OP’s case), thanks for your response, but it basically obscured the point of my post, which is:
- Templates that aren’t ran and don’t have qubes based on them
- Templates that aren’t ran, and have qubes based on them, but they’re not online*,
will never be updated, unless manually.
(this the point, it’s not about the workflow dom0 gets notification, update launcher shows up, etc, etc…)
And I’m not aware that this is documented anywhere, and I could bet most of the users are unaware of the fact, which could be considered as a security risk per se.
Even if no updates have been detected, you can use this tool to check for updates manually at any time by selecting “Enable updates for qubes without known available updates,” then selecting all desired items from the list and clicking “Next.”
And that’s all. This definitely needs terms such as “have to”, or “should” (I guess now “community made docs” are coming ahead. But how when the community was unaware of it?)
*meaning of “online” is what I’d like to test, from the beginning of the post.