[Bug 1800862] Re: Doesn't communicate about applied livepatch on start

[Sebastien Bacher]

>From the discussion on IRC, the status might be wrong after reboot since
it's only updated when livepatch apply changes

Ideally
- livepatch should delete/update that file on refresh if the status is that there is update (to check if that's not the case today)
- if the state might be wrong after reboot/new kernel deb is applied, then maybe compare uptime to timestamp of the file
- the status should maybe be deleted on reboot since the status is resetted on reboot?

Some of those issues should probably be fix to the livepatch snap

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/1800862

Title:
  Doesn't communicate about applied livepatch on start

Status in update-notifier package in Ubuntu:
  New

Bug description:
  The update-notifier livepatch code seems to only react to event, but
  since it's slow to start (it's in the graphical session and delayed by
  60s) it's likely that livepatch refresh is done before update-notifier
  is ready and such the user feedback is never send.

  We should probably change update-notifier to do send the notification
  on start if there is any applied change (it's going to nag at every
  login but that's somewhat a feature/better, since it reassure to the
  user that he has those fixes in place)

  Wdyt?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1800862/+subscriptions