On Thu, Sep 13, 2018 at 1:03 AM <mcatanzaro@gnome.org> wrote:

On Wed, Sep 12, 2018 at 8:00 AM, Bastien Nocera <bnocera@redhat.com>
wrote:
> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/a6e3ee40d90294c603e1108e19ef8fe8e6af61eb

Bastien,

It seems (a) more work is required in systemd, and (b) even if that
work were completed, it's still unsupported and expected to fail at the
kernel level.

Will you reconsider the upstream behavior?

I'd like to re-iterate that I *love* the new behavior (hibernation works perfectly on my hardware). I'd like suspend-then-hibernate to stay as an option in gnome, even if it is not the default behavior. If gnome decides to go back to standard suspend by default, can you please keep suspend-then-hibernate as an option? It would be completely fine if this wasn't even exposed in the control-center, but just in the tweak-tool or even just in dconf.

My pet peeve in gnome about this is that the hardcoded offered options don't match all the available options in systemd (for example hybrid-sleep is completely missing, and now even standard suspend is missing) and there's no viable option to configure power button/lid close behavior outside of the hardcoded options. You can configure everything in logind.conf, but gnome never lets you use that configuration, because it always consumes the event. Even if you choose "do nothing" in control-center, it consumes it and doesn't forward it to systemd (makes sense, but...). On specific hardware that I knew it needed some special treatment, I wasn't able to set the right behavior, when in gnome. It's very disappointing when you spend days or weeks debugging faulty hardware/firmware, finally arrive at a working solution, and then you're blocked by a missing item in a drop-down menu. And the only way how to make it work is to switch to a console tty before closing the lid (so that logind.conf configuration is used). Good luck teaching that your wife.

Perhaps you could simply add a dconf option to let gnome completely ignore power button/lid close signals and let systemd handle that? That would make hopefully you happy (no additional options in the gui), the power users happy (able to configure everything through logind.conf), and users with problematic hardware happy (logind.conf again, possibly after getting an advice online).