On Fri, Apr 22, 2016 at 2:24 PM, Michael Catanzaro <mcatanzaro(a)gnome.org> wrote:
On Fri, 2016-04-22 at 13:14 -0600, Chris Murphy wrote:
> This bug is proposed as a Fedora 24 blocker, anaconda component:
>
> Laptop does not resume from hibernate, boots instead
>
https://bugzilla.redhat.com/show_bug.cgi?id=1206936
My answer is that we do not support hibernation in Fedora Workstation,
so I really do not care. We do not even expose it except as the action
to perform on critical battery. It's partly because we have enough
confusing power off options, but partly because hibernation is
unreliable, hardware-dependent, and frequently broken.
Well this came up in #fedora-qa right after blocker review and
someone, maybe mcclasen (?), showed a screen shot where there was
definitely hibernation in the Power panel under Suspend & Power Off (I
know that's the 3.18 term, it's different in 3.20 but there were two
options under there, the lower one had a drop down menu that included
hibernation).
In any case, the question isn't whether hibernation is supported. It's
whether a.) it's offered by the DE by default and b.) does data loss
resulting from the failure to resume violate the data loss/corruption
release criterion and c.) is it reasonable to burden anaconda with
adding resume= to boot parameters?
The other release-blocking desktops are KDE and Xfce (on ARM); I
guess
they might care about hibernation. But they don't use this list, so I
think this isn't a good place for this discussion.
Fair enough.
--
Chris Murphy