Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!UX1.CSO.UIUC.EDU!roma From: roma@UX1.CSO.UIUC.EDU (Jon Roma) Newsgroups: comp.windows.x Subject: Re: screenblanker blanking screen at wrong times Message-ID: <9001101858.AA01896@ux1.cso.uiuc.edu> Date: 10 Jan 90 18:58:37 GMT Sender: daemon@athena.mit.edu (Mr Background) Organization: The Internet Lines: 40 > I don't think I ever saw this problem with SunOS 3.4, and I don't think I've > ever seen it with 4.0.3. That doesn't guarantee anything, by a long stretch, > but I wonder if it is specific to 3.5? It may well be, but I can't shed any light since SunOS 3.5 is the only Sun OS under which I spend any significant time running X11. > Do you mean that "xset noblank" doesn't produce the X logo screen saver? Correct. Under R3, the X logo screen saver came up, but now under R4, the screen goes completely black. I have verified that the screen saver starts up earlier than it should. The time I looked at my watch, it happened in around 7 minutes instead of the 15 minutes I specified with `xset'. As others have noted, the screen saver occasionally comes up while the user is active. As a matter of fact, this happened when I was sending this note. As I started moving the mouse, the X logo screen saver came up and then nearly instantaneously restored the normal screen contents. This problem exists both under R3 and R4. FYI, I used Sun cc to build R4. Below is output from `xset q': home 16$ xset q Keyboard Control: auto repeat: off key click percent: 0 LED mask: 00000000 auto repeating keys: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 bell percent: 100 bell pitch: 400 bell duration: 150 Pointer Control: acceleration: 4 = 4 / 1 threshold: 10 Screen Saver: prefer blanking: no allow exposures: yes timeout: 900 cycle: 120 Colors: default colormap: 0x80065 BlackPixel: 1 WhitePixel: 0 Font Path: /usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/75dpi/,/usr/lib/X11/fonts/100dpi/ Bug Mode: compatibility mode is enabled