Okay...that leaves that setting in the global options...
i assume it only influences the setting for AppVMs not any of the other things, correct?
> Okay...that leaves that setting in the global options...
> i assume it only influences the setting for AppVMs not any of the other
> things, correct?
This setting affect all the VMs at once. Qubes Manager currently doesn't
support checking the current state (which would involve checking all the
VMs and dealing with situations like enabled for some, but disabled for
others). Slightly better output you could get from `qubes-set-updates
status` command - it will show you either 'enabled', 'disabled', or
'mixed'.
The default templates definitely get checked for updates, but the cloned templates never seem to. If i manually click the "Update VM system" on a cloned template, it will often find updates.
I ran "qubes-set-update status" in dom0, and both were enabled.
Running Qubes OS 3.1
I believe its only templates that you have running at the time and connected to the internet that will get the update notice. So I only have sys-net, sys-firewall, usually running at boot. so those two templates will get checked first it seems. so one is fedora and one is debian. if one of them gets and update, I check the clones of them as well.
On another note, it would be nice to get popups to desktop or taskbar for template updates, like when there is a dom0 update. I still resort to just keeping the qubes-manager onscreen at all times. (although alsso to look for yellow triangles if any).