Whoops, I forgot that Livepatch was LTS-only. I guess that gives us more
time to fix it nicely.
I don’t see why we’d need to look at error text from the Livepatch CLI —
if we can detect that Secure Boot is on, we already know Livepatch isn’t
going to work, regardless of whether canonical-livepatch
We dont need to worry about 19.10 as Livepatches aren't produced for
non-LTS releases.
I think we need to do some research in to how to best detect if
Secureboot is enabled or not. If we can do that without too much bother
we /could/ look at that setting, and at the error text produced by the
liv
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
I've updated this wiki page:
https://wiki.ubuntu.com/Kernel/Livepatch
We can now open that URL for users when they click on /something/.
Either the bubble or the "More info" link from Software & Updates. I've
ask mpt to take a look at the design.
--
You received this bug notification because yo
We made a start on a wiki page which would detail some of this
information:
https://wiki.ubuntu.com/azzar1/Kernel/Livepatch
Could the current Livepatch wiki page be updated to include more
information about these common problem areas?
(https://wiki.ubuntu.com/Kernel/Livepatch)
We could then link
Very good feedback. Letting the user know that the livepatch failed to
apply is a good first step, but I agree that the interface should guide
the user in how to resolve the issue.
** Changed in: update-notifier (Ubuntu)
Status: New => Triaged
** Changed in: update-notifier (Ubuntu)
Im