Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: william@syma.sussex.ac.uk (William Craven)
Newsgroups: comp.sys.sun
Subject: Re: screenblank/OpenWindows problem
Keywords: Windows
Message-ID: <2238@brchh104.bnr.ca>
Date: 27 Mar 91 21:35:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 22
Approved: Sun-Spots@rice.edu
X-Original-Date: 27 Mar 91 09:29:23 GMT
X-Refs:  Original: v10n57, Replies: v10n62
X-Sun-Spots-Digest: Volume 10, Issue 70, message 2
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

From article <2093@brchh104.bnr.ca>, by jc@raven.bu.edu (James Cameron):

> Apparently, Sun's screenblanking has a *serious/silly* bug in that it
> sometimes only checks the /dev/console for messages.  The simple
> workaround is to have the Xserver (Xsun or whatever you use) run the
> screenblanking for you and disable Sun's screenblanker.  Your Xserver
> probably takes  a '-s' to get the screensaver option.

Though this bug may not be on the Sun Systems with OpenWindows but I found
with the Solbournes (Sun Clones) that if you have screenblank active and
then exit your X window session the screen hangs and you cannot return to
the terminal screen. If I have removed the screenblank daemon it works
fine such that when you leave X windows the screen no longer hangs and
returns to the ordinary terminal console. There appears to be a conflict
of access to the screen driver. It will be useful to have screenblank so
that non-X11 idle screens will be blanked out (save burning the tube and
wasting electrics over night - a lab of inverse video console screens
during the night will be enough to light up the room without having to
switch the lights on !!) Has anybody out there experienced the same
problem and if so do you have a work round ?

William Craven			william@syma.sussex.ac.uk