1. Restart icon appears to often(?)
2. Restart icon does not indicate which package(s) initiated the restart request.
3. No option to postpone restart and be asked again after predetermined amount of time.
Just for the record a kernel upgrade is NOT the only thing that can need a restart. If glibc is updated it can be extremely difficult to ensure that all old copies in use are purged without restarting the system. The same goes for any library that is loaded early in the boot process and is used by critical services.
Not restarting after akernel update could well leave your system in a big risk if the exploit is remote (e.g. in a network driver).
This is more than one bug/feature request:
1. Restart icon appears to often(?)
2. Restart icon does not indicate which package(s) initiated the restart request.
3. No option to postpone restart and be asked again after predetermined amount of time.
Just for the record a kernel upgrade is NOT the only thing that can need a restart. If glibc is updated it can be extremely difficult to ensure that all old copies in use are purged without restarting the system. The same goes for any library that is loaded early in the boot process and is used by critical services.
Not restarting after akernel update could well leave your system in a big risk if the exploit is remote (e.g. in a network driver).