Bug#971644: elogind: accidentally hitting Fn-F12 crashes the system (dirty filesystem)

[Mark Hindley]

Control: forwarded -1 https://github.com/elogind/elogind/issues/177

Thorsten,

Many thanks for this.

On Sun, Oct 04, 2020 at 01:30:53AM +0200, Thorsten Glaser wrote:
> Package: elogind
> Version: 243.7-1+debian1
> Severity: critical
> Justification: causes serious data loss
> X-Debbugs-Cc: tg at mirbsd.de

[..]

> Oct  4 01:09:22 tglase-nb vmunix: [1043273.743227] elogind-daemon[1640]: Hibernate key pressed.
> Oct  4 01:09:22 tglase-nb vmunix: [1043273.747348] elogind-daemon[1640]: Hibernating...
> Oct  4 01:09:22 tglase-nb vmunix: [1043273.749104] PM: Image not found (code -22)
> 
> This is clear evidence that elogind *actively* captured that keypress
> and did something not normal (i.e. not present on a standard pre-systemd
> system without elogind). Whatever it did apparently failed, but it STILL
> proceeded to crash the whole system (with the screen flickering a number
> of times and then the system suddenly powering off).

I fully agree that this should be handled better.

Forwarded upstream.

[...]

> I’ve also just looked at the elogind.conf file I was told to change in
> one of the two other bugreports I mentioned above. There is some config
> regarding hibernation, so I guess, now that I know about the problem,
> I could just turn off as a WORKAROUND *ONLY* (I *assume* changing
> 	#HandleHibernateKey=hibernate
> to	HandleHibernateKey=ignore
> might do the trick)

Yes, I would expect that to be a good workaround in your case.

> but then I wonder why this is not ignored by default,

If there is a consensus that the default should be different, then I am happy to
change it.

Best wishes

Mark