Like it or not, xscreensaver is an app that manages power settings based on 
parameters in the .xscreensaver file, and xscreensaver-demo is a GUI for 
editing that file.

Your complaint is that xscreensaver and various other programs that *also* try 
to manage power settings step on each others' toes.  That's unfortunate, but 
not terribly surprising, and yet, all said programs are functioning as 
designed.  You can't run two window managers at the same time, either.

You keep harping on "but I haven't clicked any of the options in 
xscreensaver-demo" but I keep trying to tell you that there's no way to tell 
what your intent is there.  xscreensaver can't tell that the various parameters 
in the .xscreensaver file haven't been changed.  It can't tell that certain 
settings in the app-defaults file are not the settings that the machine's admin 
consider to be important.  It can't tell that you happened to have manually run 
xset or some other app at some time before xscreensaver was launched and yet 
still after the latest write-date on ~/.xscreensaver or whatever.  There's no 
way to make two programs that both consider themselves to be in control of 
global settings like this both function properly.  This line of argument you 
keep making has no legs, because computers are not psychic.

I do agree that it would be a good idea for the .xscreensaver file to support 
the notion of having two different sets of settings for various parameters 
depending on whether the machine is running on battery or not.  (And for the 
xscreensaver-demo program to present a GUI for editing .xscreensaver in that 
way.)  However, it doesn't do that right now.  If someone wants to make that 
change and send me a (portable, well-commented) patch, I would be glad to 
incorporate it into xscreensaver.  I don't have time to do that work myself.

I do not think the approach of "add an option to tell xscreensaver to not do 
power management at all" is the right way to solve this problem.

(Incidentally -- and I don't consider this a "good" fix, but you might find it 
to be a workaround -- if you have a script edit the contents of ~/.xscreensaver 
when switching to/from battery power, the xscreensaver daemon will notice that 
the file has changed and re-load those settings.)




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to