GNOME Bugzilla – Bug 416429
please add Xss XScreenSaverSuspend support
Last modified: 2009-10-26 11:45:11 UTC
hi as pointed out by bug http://bugzilla.gnome.org/show_bug.cgi?id=335149 (and in many other places) , gnome-screensaver may kick in when applications do not want it to one way to solve this would be if gnome-screensaver may hook into the Xss extension of X . See http://www.die.net/doc/linux/man/man3/xss.3.html for example. Indeed there is a command XScreenSaverSuspend that may be used by applications that do not want gnome-screensaver (or, any other screensaver) to start.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Also see: http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#head-e2151a3d8feaaab341a17b9529529b80438b3cae *** This bug has been marked as a duplicate of 346806 ***
Hi. Sorry to bring up this old bug, but I don't think it's a dupe of 346806 (at least not any more). Some applications (notably mplayer) still only use XScreenSaverSuspend to indicate that they don't want the screen saver to be activated. This can lead to frustrating situations when watching movies with friends, for example. Even though gnome-screensaver has decided not to use the inbuilt X screensaver support, and for good reasons, it should still try to hook in and detect XScreenSaverSuspend, if that is possible - if it's not, perhaps this needs to be fixed in the X server. It's all well and good for applications to use gnome-screensaver's DBus API to say they don't want the screensaver to come on, but applications need a way to tell all screensavers, not just specific ones it knows about. Having an API in X for this is really the best way to do it, and possibly XScreenSaverSuspend is already that API.