Notifies multiple times that the machine needs rebooting

Bug #22105 reported by Crispin Flowerday on 2005-09-20
8
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Medium
Michael Vogt

Bug Description

I know that individual packages tell the update-notifier process what to show,
but potentially now, after a system upgrade, you could be told multiple times
that you need to reboot (e.g. kernel, hal, dbus).

Wouldn't it be better to have each of those packages touching a file that
update-notifier spots, and then update-notifier gives a single stock warning
telling the user to reboot.

Michael Vogt (mvo) wrote :

Thanks for your bugreport.

update-notifier can't enforce a policy here. It tries it's best to not show
duplicates (e.g. by checking for identical notifications and skiping them).

Just to flesh my idea out:

When a package requires a reboot for it work properly, it creates an empty file
(e.g. "/var/lib/update-notifier/require-reboot")

update-notifier spots this and then shows a 'stock' notification text, e.g:

--
<b>Reboot required</b>

Parts of your base system have been upgraded. You should
reboot your machine soon to ensure the upgrades are effective.
--

Once the message has been shown to the user (or a reboot happens),
update-notifier would remove the file.

Although (obviously) update-notifier can't enforce this policy, there could be
an ubuntu policy so that all the ubuntu packages that need reboots just have to
touch the file. I just didn't like being told that dbus needed a reboot, and
immediately hal needed one :-)

Michael Vogt (mvo) wrote :

Thanks for this additional data.

I like the idea of having a pre-defined hook for this very common task. Asking
that a reboot is required seems to be the most common action for update-notifier
these days.

Michael Vogt (mvo) wrote :

This problem is solved, packages should use:

 /usr/share/update-notifier/notify-reboot-required

to notify about reboot requirements.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.