[Trac #1429] Screen saver needs implementation...

[Zarro Boogs per Child]

#1429: Screen saver needs implementation...
------------------------------+---------------------------------------------
  Reporter:  jg               |       Owner:  JordanCrouse
      Type:  defect           |      Status:  assigned    
  Priority:  high             |   Milestone:  BTest-4     
 Component:  x window system  |     Version:              
Resolution:                   |    Keywords:  power       
  Verified:  0                |  
------------------------------+---------------------------------------------
Comment (by jg):

 Power managers interact with dbus these days to set such policy: and they
 use the dpms interface for controlling the monitors and flatpanels they
 support.  This is how things like Totem tell the desktop not to invoke the
 screen saver on them.

 So yes, the policy is set in a power management daemon on modern X
 desktops already.  But I see no reason to implement it behind X's back, as
 X needs to be able to immediately wake up the system and light up the
 screen on user input (I don't want to add the latency of talking to an
 external daemon to that operation, nor the failure case of the screen
 failing to go back on because the power manager daemon is wedged) in the
 dcon case we already have hardware support to turn the screen back on
 immediately without waiting the frame latencies to reassert Geode control
 over the screen.

 It may be that the dcon portion of the X driver should directly substitute
 its functions for dpms functions that normally talk to DPMS monitors and
 flatpanels; but I think it does belong in X, not done behind X's back.

 In short, I see no good reason to do a one-off OLPC hack from the
 standpoint of the application environment; the architecture is there
 already, and it is failsafe so long as the X server is running (much more
 likely than the rest of the environment).

-- 
Ticket URL: <http://dev.laptop.org/ticket/1429#comment:4>
One Laptop Per Child <http://laptop.org/>