If you aren’t signed in to Ubuntu One, that’s not an “error”, it’s just a reason that you can’t use Livepatch right now. So we make you sign in before turning on Livepatch in the first place. And if you become signed-out after Livepatch is turned on, a dialog should direct you back to the settings to resolve the situation (though it seems I never specced the dialog part, oops).
I think the same applies to having Secure Boot on without the Livepatch key imported. It’s a situation we understand, and there is a way to fix it, so it needn’t be a grumpy “error”, it’s just a reason that you can’t use Livepatch right now. (That the moment we discover it happens to be while applying an update is an implementation detail, it’s not the fault of that particular update.) We could guide you to import the key, then restart, before turning on Livepatch in the first place. And if you turn on Secure Boot — or un-import the key? — after Livepatch is turned on, a dialog could direct you back to the settings to resolve the situation. Questions: 1. Is that approach practical? That is, detect Secure Boot and key- import state whenever you navigate to this settings tab, with a button to open a PolicyKit dialog for you to import the key then restart. And an equivalent button in a dialog if a Livepatch update doesn’t apply for that reason. 2. If it is practical, should I go ahead and design it in more detail, or is it so complicated + common that we need temporary help text instead for 19.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833277 Title: LIvepatch widget should link to secure boot information on error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1833277/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
