| 2012-04-24 07:13:00 |
ceg |
bug |
|
|
added bug |
| 2012-04-24 07:17:40 |
ceg |
bug task added |
|
qt-shutdown-p |
|
| 2012-04-25 06:39:35 |
ceg |
description |
Linux provides a simple way to schedule a restart event.
rtcwake -m on -s <seconds-to-sleep>
This particular command avoids that rtcwake does any switching into another power
state (mode -m stays on).
It allows the power state to be handled by the regular installed power managment
tools, which is more stable especially on resume.
Just schedule the wake event, then do the regular shutdown/suspend.
Later, the real time clock will trigger the scheduled power event
and the machine comes back up. |
Linux provides a simple way to schedule a restart event.
rtcwake -m on -s <seconds-util-start-event>
This particular command avoids that rtcwake does any switching into another power
state (mode -m stays on).
It allows the power state to be handled by the regular installed power managment
tools, which is more stable especially on resume.
Just schedule the wake event, then do the regular shutdown/suspend.
Later, the real time clock will trigger the scheduled power event
and the machine comes back up. |
|
| 2012-04-25 19:33:55 |
ceg |
bug task added |
|
consolekit (Ubuntu) |
|
| 2012-04-25 19:39:58 |
ceg |
description |
Linux provides a simple way to schedule a restart event.
rtcwake -m on -s <seconds-util-start-event>
This particular command avoids that rtcwake does any switching into another power
state (mode -m stays on).
It allows the power state to be handled by the regular installed power managment
tools, which is more stable especially on resume.
Just schedule the wake event, then do the regular shutdown/suspend.
Later, the real time clock will trigger the scheduled power event
and the machine comes back up. |
Linux provides a simple way to schedule a restart event that is particularly usfull in conjuction to initiating or scheduling a shutdown or suspend.
rtcwake -m on -s <seconds-util-start-event>
Howerever, just as the shutdown command it requires root privileges.
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 the power state fully handled by the regular installed power managment (userspace) tools, which is often more stable than the pure kernel/rtcwake, especially on resume.
To test it, just schedule a wake event, then do a regular shutdown/suspend. Later, the real time clock will trigger the scheduled power up event and the machine comes back up. |
|
| 2012-04-25 19:40:35 |
ceg |
description |
Linux provides a simple way to schedule a restart event that is particularly usfull in conjuction to initiating or scheduling a shutdown or suspend.
rtcwake -m on -s <seconds-util-start-event>
Howerever, just as the shutdown command it requires root privileges.
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 the power state fully handled by the regular installed power managment (userspace) tools, which is often more stable than the pure kernel/rtcwake, especially on resume.
To test it, just schedule a wake event, then do a regular shutdown/suspend. Later, the real time clock will trigger the scheduled power up event and the machine comes back up. |
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>
Howerever, just as the shutdown command it requires root privileges.
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 the power state fully handled by the regular installed power managment (userspace) tools, which is often more stable than the pure kernel/rtcwake, especially on resume.
To test it, just schedule a wake event, then do a regular shutdown/suspend. Later, the real time clock will trigger the scheduled power up event and the machine comes back up. |
|
| 2012-04-25 20:03:31 |
hakaishi |
bug task added |
|
gnome-session-shutdown |
|
| 2012-04-25 20:09:10 |
Launchpad Janitor |
consolekit (Ubuntu): status |
New |
Confirmed |
|
| 2012-04-29 21:59:20 |
Jacopo Lorenzetti |
gnome-session-shutdown: status |
New |
Invalid |
|
| 2012-04-30 10:55:37 |
ceg |
description |
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>
Howerever, just as the shutdown command it requires root privileges.
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 the power state fully handled by the regular installed power managment (userspace) tools, which is often more stable than the pure kernel/rtcwake, especially on resume.
To test it, just schedule a wake event, then do a regular shutdown/suspend. Later, the real time clock will trigger the scheduled power up event and the machine comes back up. |
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>
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. |
|
| 2012-04-30 11:08:33 |
ceg |
bug task added |
|
xfdesktop4 (Ubuntu) |
|
| 2012-05-10 09:11:08 |
ceg |
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 on -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. |
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).
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. |
|
| 2012-05-10 09:11:45 |
ceg |
summary |
allow to set restart/resume time |
allow to set restart/resume time in shutdown dialog |
|
| 2012-05-10 09:13:05 |
ceg |
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 (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. |
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. |
|
| 2012-05-11 20:16:22 |
Jacopo Lorenzetti |
bug task deleted |
gnome-session-shutdown |
|
|
| 2012-05-16 14:21:04 |
Lionel Le Folgoc |
bug task deleted |
xfdesktop4 (Ubuntu) |
|
|
| 2017-06-11 11:33:32 |
hakaishi |
bug task deleted |
qt-shutdown-p |
|
|
