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 is running at the moment. Meanwhile, it occurs to me that for “a dialog if a Livepatch update doesn’t apply”, that dialog could be the Software Updater prompt — which is going to appear anyway, and already promotes Livepatch if it’s off (cf. bug 1807900), and should therefore be smart enough to do something different if Livepatch is turned on but not working. That would avoid any increase in total interruptions. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
