Hi, I have also been following this bug. I think Steve wrote things down pretty nicely, just see one small comment below.
On Sun, Nov 29, 2009 at 1:44 PM, Steve Dodier <sidnio...@gmail.com> wrote: > [SNIP] > > Also, xscreensaver has a GUI for modifying some of these settings; Alright. > But, be it a GUI or a CLI, an interface is meant to change settings *when it > is used*, and certainly not to regularly change them again *in the > background, without user consent*; You may not agree with me on this but I > think pretty much everyone would. It sounds perfectly normal to me that when > data used by an app changes, then the app has to adapt to these changes > instead of bluntly reverting them to it's convenience. There can be > incompatibilities between applications, but I think the actual problem here > is that xscreensaver reverts the settings instead of changing it's own > internal data to reflect external changes. I'd say the solution is much more simple - it would be nice if xscreensaver had an option, be it in the GUI, cli or compile-time only, to "not touch DPMS settings". That should be much simpler to implement than any monitoring (which would have the race conditions mentioned earlier). It would be great for i.e. xfce users to see this implemented. They could continue to use the screensaver they trust, while being able to modify settings using tools from their DE. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
