Problems with Screensavers and other activity sensitive demons.
graeme2 at argyllcms.com
Thu Jun 7 19:20:28 PDT 2007
Carsten Haitzler (The Rasterman) wrote:
> On Thu, 07 Jun 2007 02:02:01 +1000 Graeme Gill <graeme2 at argyllcms.com> babbled:
> XScreenSaverSuspend(). it's there. it's engineered. it's documented. the
> problem lies not in lack of engineering in the X11 department. its a very
> clean implementation and exactly what you need. if screensaver apps are hacking
> around the xscreensaver extension and not using XScreenSaverSelectInput() +
> XScreenSaverNotifyEvent's - then they need to be corrected ad they simply are
> not playing nice (tm).
Thank's for drawing this to my attention - I wasn't aware XScreenSaverSuspend()
had been introduced in the X11R7.1 release. It does look like it will solve
a lot of future issues like the ones I've run across. Unfortunately
it doesn't help anyone not running X11R7.1 or latter yet, and the current
hacks will therefore have to stay in place. Similarly, the xscreensaver
and GnomeScreensaver documentation don't seem to make any reference
to XScreenSaverSuspend() yet, instead pointing to the control programs
Is it likely that XScreenSaverSuspend() will disable power savers as well ?
More information about the xdg