On Wed, Apr 04, 2001 at 12:06:18AM -0400, Noah L. Meyerhans wrote: > On Tue, Apr 03, 2001 at 07:33:08PM -0700, Eric G. Miller wrote: > > Yea, think this is something with the X screensaver. X screensaver > > probably kicks on at 10 minutes, and doesn't go to Standby 'til 30 > > minutes. Seems the two need to get in sync... > > That should not be the case. According to the xscreesaver man page, > xscreensaver should notice when the X server has kicked in DPMS and shut > the monitor off. It doesn't manipulate dpms at all. See the "POWER > MANAGEMENT" section of the man page. > > One very odd thing is the output that 'xset q' gives during this whole > process. Say I first do 'xset dpms 60 300 600' followed by 'xset q' I > see what I expect: > DPMS (Energy Star): > Standby: 60 Suspend: 300 Off: 600 > DPMS is Enabled > Monitor is Off > > However, a few minutes later, 'xset q' gives totally different results: > DPMS (Energy Star): > Standby: 10 Suspend: 10 Off: 10 > DPMS is Disabled
There was a thread about this a week or 2 ago, & it was xscreensaver that was causing dpms to be disable. I think Karsten file a bug against xscreensaver. John > > I could understand if I was running something like GNOME or KDE that > they might want to manage DPMS on their own, and could screw up some of > my settings, but I'm not using them. The only clients are xscreensaver, > some Eterms, Window Maker, xconsole, and xset. > > This strikes me as strange enough to possibly warrant a trip out of the > comfy confines of the familiar Debian lists and into the unexplored > region of the XFree86 mailing lists. 8^) > > noah > > -- > _______________________________________________________ > | Web: http://web.morgul.net/~frodo/ > | PGP Public Key: http://web.morgul.net/~frodo/mail.html > -- -_-_-_-_-_-_- Using Linux _-_-_-_-_-_-_