[Bug 1998947] Re: restore reboot notification so that users are notified after unattended-upgrades

[Robie Basak]

There seems to be quite a bit of iteration in this area in the stable
releases at the moment - see for example bug 1747499 and the subsequent
regression report bug 2017401.

So how would this proposed change interact with livepatch?

In principle I think it's OK to SRU this type of thing, but I'd prefer
to see a broad specification document that describes how we intend all
these different components to interact before considering further
individual SRUs.

** Changed in: update-notifier (Ubuntu Jammy)
       Status: In Progress => Incomplete

** Changed in: update-notifier (Ubuntu Lunar)
       Status: In Progress => Incomplete

-- 
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/1998947

Title:
  restore reboot notification so that users are notified after
  unattended-upgrades

Status in update-notifier package in Ubuntu:
  Fix Released
Status in update-notifier source package in Jammy:
  Incomplete
Status in update-notifier source package in Lunar:
  Incomplete

Bug description:
  [Impact]

  There is not currently a user-friendly way to be notified that a
  reboot is required as a result of a package that was upgraded during
  unattended-upgrades. The reboot notification in update-notifier that
  was removed long ago would serve this purpose.

  The main rationale for this is that we needed to enable this for a
  special jammy-based customer and we do not want this functionality to
  regress whenever a new update-notifier is released. We think that this
  change will benefit all Ubuntu users. It does change the behavior, but
  we think it's a change that is acceptable.

  We're open to discussion with the SRU team about this.

  [Test Plan]

  1. Install update-notifier from jammy-proposed.
  2. Reboot
  3. Install a package, or install updates, so that /var/lib/dpkg/info is updated.
  4. If needed, touch /var/run/reboot-required (this might actually happen depending on what you install/update).
  5. Wait 3 hours for the reboot notification to appear.
  6. Click on the notification icon to show the option to reboot, and click on that.

  [Where problems could occur]

  Bringing back old code may reveal bugs in the old code that would have
  been found if it was maintained all this time. Besides that, if we saw
  regressions introduced by this it would likely be related to the
  monitoring of other files.

  [Other information]

  We are mainly interested in SRU'ing to Jammy because that's where the
  use case exists, but we can keep Lunar up-to-date as well.

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