Description of problem:
Assume that some xscreensaver application it creating problems
and that one tries to turn it off either via preference settings
or calling xscreensaver-demo directly; which boils down to the
same. Even just touching a check button to turn that off brings
up that troublesome program in question and if this locks up
a machine (which just happened to me due, turned out, to test
of some development kernels) then one is stuck in an "interesting"
chicken-or-egg problem. If moreover "Only One Screen Saver" with
a "wrong" entry was put there then just attempting to open
a configuration is locking up the whole thing.
One can get out from that vicious cirle by directly editing
~/.xscreensaver file but this is not entirely obvious that one
should look just there and not in some gconf entries. It would
be nice to have _at least_ some delay to allow to change some
settings without triggering troubles.
Version-Release number of selected component (if applicable):
Adding artificial delays to get around lock up problems is probably
not the best approach. A better approach would be to fix the lock up
problems. Any lock up problems should be fixed on a case-by-case
basis in separate bug reports, of course.