hibernation redux, possible blocker bug
Another hibernation bug came up for blocker review today.
systemd-logind does not verify if system has resume device defined
when checking if can.hibernate or can.hybridsleep
https://bugzilla.redhat.com/show_bug.cgi?id=1332266#c6
Converse to the description, the most compelling aspect is the
screenshot in comment 6, in which GNOME shell puts up a notification
stating that the system will hibernate soon. But of course that can't
work on Fedora right now because the required command line
"resume=<swap>" does not exist.
QA is right on the fence whether this behavior is sufficiently
misleading and bad as to violate the data corruption/loss release
criterion. In reality the system will merely be shutdown, so why not
just say that?
https://fedoraproject.org/wiki/Fedora_24_Final_Release_Criteria#Data_corr...
Question for the WG is, is is possible to change
/etc/UPower/UPower.conf such that
- CriticalPowerAction=HybridSleep
+ CriticalPowerAction=PowerOff
That way the misleading message shouldn't happen?
--
Chris Murphy