On dim., 2010-08-01 at 19:20 +0200, Vincent Bernat wrote: > When using -mode blank, the default should not be DPMS. IMO, this is > not the job of a screensaver to handle DPMS since X server is already > handling it.
Hey, to be honest, I quite like the DPMS behavior (especially since there's no real need to wait for X server to do it when the screen is blanked). > > With the default configuration, xlock seems to go directly in deep > DPMS mode as soon as it kicks in. If I hit a key as soon as it starts, > it takes 5 seconds to come back. For the CRT (and some LCD maybe) cases which are long to resume, it could have been better to make it configurable (this is what I proposed in #558695) > I think that the LCD panel is turned > off then on again. To my knowledge, LCD panels support a limited > on/off cycles. > Yup, I experienced that too. In fact, depending on the runs it's not the same, but I just experienced: Before: mardi 17 août 2010, 20:11:19 (UTC+0200) DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 900 DPMS is Enabled Monitor is On Run xlock, screen is locked, but still on: mardi 17 août 2010, 20:11:22 (UTC+0200) DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 30 DPMS is Enabled Monitor is On we can see that DPMS off time was reduced to 30s, but monitor is still on. Touching a key DPMS off the screen and resume it instantly, prompting for a password. Then the screen is unlocked: mardi 17 août 2010, 20:11:30 (UTC+0200) DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 900 DPMS is Enabled Monitor is On and DPMS off time is reset to what it was before. Not every run gives that behavior, sometime the screen is correctly shut down. I'll try to look at source code to see what causes that inconsistency, but that might deserve another bug report. Cheers, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
