On 05/30/2014 09:20 AM, Michael Biebl wrote:
> 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
Ah, that could be. I don't use Gnome.
>> - 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.
Well, in my case I'm calling 'systemctl hibernate' from the command
line, so a simple message to the console would do.
> 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)
Agreed, a desktop environment should check for /run/do-not-hibernate and
don't even try to hibernate if it exists. But I think that's orthogonal
to having the 'systemctl hibernate' command do the same check and refuse
with an error message to the console.
Best,
Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
