Well at least with what's upstream it's not working with what was committed for me.
The other problem I find is that gnome-power-manager sets some policy actions and systemd sets others. For example systemd is controlling the lid action but gnome power manager is controlling the timeout action. The action is hardcoded right now in systemd. So unless systemd adopts a similar prefer suspend then hibernate over suspend policy if possible this could cause a confusing experience. On Tue, May 1, 2018 at 10:11 AM Sebastien Bacher <seb...@ubuntu.com> wrote: > The changes got commited to upstream master, we might want to > backport/SRU in bionic? > > ** Changed in: gnome-settings-daemon (Ubuntu) > Importance: Undecided => Wishlist > > ** Changed in: gnome-settings-daemon (Ubuntu) > Status: New => Triaged > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1756006 > > Title: > FFe: Support suspend-then-hibernate > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions > -- Mario Limonciello supe...@ubuntu.com -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-then-hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs