On Tue, 2018-10-02 at 12:53 +0200, Hans de Goede wrote:
On 01-10-18 16:14, Justin Forbes wrote:
> On Sun, Sep 30, 2018 at 1:52 PM, Hans de Goede <hdegoede(a)redhat.com> wrote:
> > Hello Fedora kernel team,
> > On the Fedora desktop list there has been a discussion about
> > systemd now offering a new suspend-then-hibernate option and
> > gnome-settings-daemon's media-keys plugin using this when
> > the power-button gets pressed and systemd saying this is
> > available on the system.
> > What this does is suspend the system normally and set
> > a RTC wakeup 3 hours in the future, then when the RTC wake
> > happens it hibernates the system.
> > As discussed on the desktop list this is not really desirable
> > as default behavior for F29 (and later) since the hibernate
> > code is not really something which gets used enough to be
> > well tested and is really not something which we can support.
> > So after that the discussion has gone in the direction of
> > how to disable the new suspend-then-hibernate behavior.
> > Lennart made a really interesting observation here, systemd
> > is just proxying if "cat /sys/power/disk" indicates that
> > hibernate is supported.
> No, that is not what systemd is doing. The kernel provides a
> mechanism, it does absolutely nothing with that mechanism unless told
> to do so. What systemd is actually doing is creating a policy around
> that mechanism.
systemd is really *not* creating policy here, it has a DBUS API
call called CanHibernate which really just proxies what the kernel
What if we renamed it "MightHibernate"? :)
(only sort-of kidding...)
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net