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

Nick Rosbrook 1998947 at bugs.launchpad.net
Mon Jul 31 19:53:01 UTC 2023


** Description changed:

  [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.
  
  [Test Plan]
- TODO
+ 
+ 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 only interested in SRU'ing to Jammy because that's where the use
+ case exists. We are OK with the fact that this behavior will be omitted
+ from Lunar.

-- 
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:
  New

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.

  [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 only interested in SRU'ing to Jammy because that's where the
  use case exists. We are OK with the fact that this behavior will be
  omitted from Lunar.

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




More information about the foundations-bugs mailing list