Am 30.05.2014 17:58, schrieb Nikolaus Rath: > > - new kernel is silently installed by unattended-upgrades (apparently > this happens even when the new package breaks the ABI) and becomes the > default to be loaded by the bootloader > - there's no visible indication that this happened, so I hibernate as usual
IIRC under GNOME we show a reboot required notification when a new kernel is installed > - when I reboot, I automatically end up with the new kernel (still > without me being aware of it) Well, the grub menu entry carries the kernel version in the description. But I acknowledge that one can miss that. > - when the resume fails and the system reboots again, I realize that > there is a problem, but at that point it's too late. I can no longer > resume, and the hibernated system state is lost. The problem with simply doing nothing on hibernate when /run/do-not-hibernate exists, is that this is also not visible to the user since there there is no API to communicate that to the user why hibernate did not succeed. I think the only practical solution to this, is if the desktop environment warns/informs you about this issue (and ideally disables the hibernate functionality) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
