xset not working on session start

[Glynn Clements]

Atom Smasher wrote:

> > IOW, something else is changing the settings. In which case, you have 
> > three options:
> >
> > 1. Figure out what is changing the settings, and disable it.
> >
> > 2. Figure out what is changing the settings, and configure it to use 
> > your preferred settings (thus eliminating the need to use xset).
> ========================
> 
> i like your logic, but i'm not sure how to go about finding what is 
> changing the settings. any suggestions?

I don't have anything better than trial-and-error, i.e. disable stuff
until it stops happening, then re-enable things in the reverse order
until it starts happening again.

[FWIW, I gave up on KDE because of something similar; *something* was
setting X resources, and I spent nearly two days trying to figure out
*what*, with no success.]

> i'm still curious why the settings are getting hosed unless first adding a 
> delay. the only things i can think of if my fancy-schmancy window manager 
> (e16) or xscreensaver... but with this script:
> 
> #!/bin/sh 
> Xnest :3 -ac &
> xterm -display :3 -e 'xset b 98 432 123 m 4/1 8 ; /usr/local/bin/xscreensaver' &
> xterm -display :3 -e 'e16' &
> xterm -display :3 -geometry -180+119
> 
> i couldn't duplicate the problem. i ran the script several times, and 
> every time i typed 'xset q' into the xterm i got the numbers i set just 
> before starting xscreensaver & e16.

My first guess would be the WM, or something which it runs. A
screensaver might conceivably change the DPMS settings, but I doubt
that it would change the bell or mouse settings.

It's possible that the WM behaves differently on different displays
(e.g. one config for the "main" session and a different config for
"additional" sessions). Or it's being done by some utility which
explicitly prevents multiple instances for a single user.

-- 
Glynn Clements <glynn at gclements.plus.com>