[Bug 987664] Re: allow to set restart/resume time

[ceg]

** Description changed:

  The desktop environments would help saving energy, if their shutdown
  dialogs could by default provide the option (button/checkbox) to
  schedule a restart.
  
  Linux provides a simple way to schedule a restart event that is
  particularly usefull in conjuction with initiating or scheduling a
  shutdown or suspend.
  
- rtcwake -m on -s <seconds-util-start-event>
+ rtcwake -m no -s <seconds-util-start-event>
  
  Howerever, just as the shutdown command it requires root privileges.
  Thus the need for a similar consolekit support.
  
  The particular command given in the example above avoids that rtcwake does any switching into another power state (mode -m stays on).
  This allows that all power state switching is still contolled by whatever  power management (userspace) tools are installed, which may often be more stable than the pure kernel/rtcwake method, especially on resume.
  
  To test it, just schedule a wake event like above as root, then do a
  regular shutdown/suspend. Wait, and watch how the real time clock
  triggers the scheduled power up event and the machine comes back up.

** Summary changed:

- allow to set restart/resume time
+ allow to set restart/resume time in shutdown dialog

** Description changed:

  The desktop environments would help saving energy, if their shutdown
  dialogs could by default provide the option (button/checkbox) to
  schedule a restart.
  
  Linux provides a simple way to schedule a restart event that is
  particularly usefull in conjuction with initiating or scheduling a
  shutdown or suspend.
  
  rtcwake -m no -s <seconds-util-start-event>
  
  Howerever, just as the shutdown command it requires root privileges.
  Thus the need for a similar consolekit support.
  
- The particular command given in the example above avoids that rtcwake does any switching into another power state (mode -m stays on).
+ The particular command given in the example above avoids that rtcwake does any switching into another power state (no new mode "-m no").
  This allows that all power state switching is still contolled by whatever  power management (userspace) tools are installed, which may often be more stable than the pure kernel/rtcwake method, especially on resume.
  
  To test it, just schedule a wake event like above as root, then do a
  regular shutdown/suspend. Wait, and watch how the real time clock
  triggers the scheduled power up event and the machine comes back up.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to consolekit in Ubuntu.
https://bugs.launchpad.net/bugs/987664

Title:
  allow to set restart/resume time in shutdown dialog

Status in GNOME Session Shutdown:
  Invalid
Status in Qt projects from Hakaishi:
  New
Status in Shutdown Timer Extension for GNOME shell:
  New
Status in “consolekit” package in Ubuntu:
  Confirmed
Status in “xfdesktop4” package in Ubuntu:
  New

Bug description:
  The desktop environments would help saving energy, if their shutdown
  dialogs could by default provide the option (button/checkbox) to
  schedule a restart.

  Linux provides a simple way to schedule a restart event that is
  particularly usefull in conjuction with initiating or scheduling a
  shutdown or suspend.

  rtcwake -m no -s <seconds-util-start-event>

  Howerever, just as the shutdown command it requires root privileges.
  Thus the need for a similar consolekit support.

  The particular command given in the example above avoids that rtcwake does any switching into another power state (no new mode "-m no").
  This allows that all power state switching is still contolled by whatever  power management (userspace) tools are installed, which may often be more stable than the pure kernel/rtcwake method, especially on resume.

  To test it, just schedule a wake event like above as root, then do a
  regular shutdown/suspend. Wait, and watch how the real time clock
  triggers the scheduled power up event and the machine comes back up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session-shutdown/+bug/987664/+subscriptions