On Thu, Apr 12, 2018 at 12:41:30PM -0000, Jeremy Bicha wrote:
> Resetting to New since the g-s-d commits have been accepted upstream.
> They are the first 4 commits for 12 Apr, 2018.
> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commits/master

The new version is to automatically select this policy if systemd
supports it, right?

What makes systemd answer yes to that question? Is there a chance that
existing machines could start using this and it could be broken for


Iain Lane                                  [ i...@orangesquash.org.uk ]
Debian Developer                                   [ la...@debian.org ]
Ubuntu Developer                                   [ la...@ubuntu.com ]

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

  FFe: Support suspend-then-hibernate

Status in gnome-settings-daemon package in Ubuntu:
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to