Re: X Server Crashing on DPMS Event

2004-06-06 Thread Erik Steffl
Barry Skidmore wrote: When I did a: # xset -dpms xserver immediately crashed with the following error: xterm: fatal IO server error 32 (Broken pipe) or KillClient on X Server ":0.0" /usr/bin/Windowmaker warning.got signal 1 (Hangup1-exiting... looks like it's confirmed that it has something to do

Re: X Server Crashing on DPMS Event

2004-06-06 Thread Barry Skidmore
When I did a: # xset -dpms xserver immediately crashed with the following error: xterm: fatal IO server error 32 (Broken pipe) or KillClient on X Server ":0.0" /usr/bin/Windowmaker warning.got signal 1 (Hangup1-exiting... Barry On Sun, Jun 06, 2004 at 08:30:15PM -0500, Barry Skidmore wrote: >

Re: X Server Crashing on DPMS Event

2004-06-06 Thread Barry Skidmore
No, I am not sure it is dpms that is causing the problem, but I will see what is the effect of the -dpms option. I did not see that option documented. Barry On Sun, Jun 06, 2004 at 04:30:22PM -0700, Erik Steffl wrote: > Barry Skidmore wrote: > >I believe I am having a problem with the xserver fa

Re: X Server Crashing on DPMS Event

2004-06-06 Thread Erik Steffl
Barry Skidmore wrote: I believe I am having a problem with the xserver failing whenever my monitor's DPMS kicks in. After either windowmaker or enlightenment have run for 15 minutes, the window manager quits and I am put back into the console with the following errors: Fatal server error: Cau

X Server Crashing on DPMS Event

2004-06-06 Thread Barry Skidmore
I believe I am having a problem with the xserver failing whenever my monitor's DPMS kicks in. After either windowmaker or enlightenment have run for 15 minutes, the window manager quits and I am put back into the console with the following errors: Fatal server error: Caught signal 4. Server