Package: update-notifier Version: 0.42.12-2+b1 Priority: wishlist Update-notifier suggests that the system needs to be restarted without giving any indication if this is because:
- a new kernel has been installed
- a basic component (such as the libc) has been updgraded
I understand (from looking into the sources) that it is checking out the
/var/run/reboot-required but it is not clear to me who is supposed to do
this.
For example, I see this:
$ find /var/lib/dpkg/info/ -type f -exec grep -l
/usr/share/update-notifier/notify-reboot-required {} \;
/var/lib/dpkg/info/dbus.postinst
/var/lib/dpkg/info/initscripts.postinst
Certainly, a dbus update does not require a reboot of the full system (but it
might require a desktop restart). As for initscripts, reading the postinst
code it is clear to me why it needs to be restarted.
Could there be some way for the scripts using
/usr/share/update-notifier/notify-reboot-required to add a message explaining
*why* they think a reboot is required?
Should there should be a
/usr/share/update-notifier/notify-desktop-restart-required program which could
be used by core desktop components to tell you that you have to restart the
*desktop* and not the system? (it looks like that should be done by Dbus)
Regards
Javier
signature.asc
Description: Digital signature
