In <[EMAIL PROTECTED]>, Francesco Poli wrote: > On Fri, 4 May 2007 15:29:42 -0700 Jamie Zawinski wrote: > > > The way mplayer disables xscreensaver is idiotic, so it would not be > > at all surprising that mplayer would also screw up your dpms settings. > > > > The only sensible way for a video player to interact with > > xscreensaver: http://www.jwz.org/xscreensaver/faq.html#dvd > > > > The mplayer developers are aware of this, and don't care.
The trouble is xscreensaver isn't the only screensaver; you can also configure screen blanking and DPMS with xorg.conf/XF86Config or with some functions in XLib etc. With this method I don't have problems with video players etc. All SDL does is use standard X calls to disable blanking and DPMS while it's running then reenable them when it exits. When xscreensaver's running it ignores the X setting and blanks the screen anyway, but somehow DPMS is left permanently disabled. I was really only using xscreensaver because I thought Gnome was forcing me to, but I've just found out that fortunately I can just uninstall xscreensaver without any real gnome packages depending on it. Perhaps when set to "blank only" it could use X's built-in screensaver instead of its own daemon so that novice Gnome users can still have the same GUI to set the timeouts but avoid problems. > Maybe Debian mplayer package maintainers could be persuaded to create a > Debian patch that fixes this issue for Debian... > > Would it be possible? And SDL and gxine (and other xines? and totem?) etc etc. Wouldn't it be possible to get xscreensaver to call XGetScreenSaver() before blanking or running a saver and realise it shouldn't do anything if another application has disabled blanking? Or does xscreensaver itself disable blanking with XSetScreenSaver() so the X blanking doesn't interfere with it? -- TH * http://www.realh.co.uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
