Ah, well spotted. Several programs should vary their UI depending on whether canonical-livepatch is installed. update-manager is one of them (this bug); software-properties is another; and gnome-initial-setup is another.
Bug 1770686 reveals that the Livepatch settings in software-properties depend, in turn, on the gnome-online-accounts-panel in gnome-control-center. This isn’t a package-level dependency: you can still install and use software-properties without gnome-online-accounts, you just don’t see the Livepatch feature. So I guess anything linking to the software-properties Livepatch UI should check for the existence of that panel *and* of software-properties itself.
That doesn’t change the UI design for this bug (if you can’t turn on Livepatch, it’s not “available”), but it will affect the implementation.
Ah, well spotted. Several programs should vary their UI depending on whether canonical-livepatch is installed. update-manager is one of them (this bug); software-properties is another; and gnome-initial-setup is another.
Bug 1770686 reveals that the Livepatch settings in software-properties depend, in turn, on the gnome-online- accounts- panel in gnome-control- center. This isn’t a package-level dependency: you can still install and use software-properties without gnome-online- accounts, you just don’t see the Livepatch feature. So I guess anything linking to the software-properties Livepatch UI should check for the existence of that panel *and* of software-properties itself.
That doesn’t change the UI design for this bug (if you can’t turn on Livepatch, it’s not “available”), but it will affect the implementation.