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 with dpms.however the errors above are not from X server, these are just errors from X clients (xterm and Windowmaker) essentially complaining that X server is gone.
check the /var/log/XFree86.0.log and /var/log/xdm.log for X server errors. Try to search google for the error, that helps sometime. Also try to search for X config info specific to your video card (don't think the monitor matters).
erik
Barry On Sun, Jun 06, 2004 at 08:30:15PM -0500, Barry Skidmore wrote: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 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:are you sure it's dpms that causes the problem?--To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org