🚀 go-pugleaf

We sometimes use the console of a VGX Iris here, running 4.0.5,
for single-frame video recording.  The recording software used to call just
	blanktime(0);
at the beginning of a session to ensure that (a) the screen was not blanked
and (b) it would stay that way.  (Since the screen is unviewable while
recording, we'd often run recording jobs remotely, so the console could well
have been idle long enough to go blank.)

Calling blanktime(0) alone worked under 3.3 and (I think) 4.0.1.
But, when we upgraded to 4.0.4, it stopped working.  Apparently if the
display was already blanked, blanktime(0) would *not* re-enable it, and we'd
spend hours recording only to find black video.  So I changed that to
	blankscreen(FALSE);
	blanktime(0);
but this was (sometimes? always?) ineffective -- the screen would remain blank. 

Often we'd then find it impossible to *unblank* the screen -- pounding on the
keyboard had no effect, and we'd have to kill the X server or reboot.
(Yes, /etc/config/system.glGammaVal was intact.)

After some frustrating months I stumbled on this workaround (!):
	blankscreen(TRUE);
	blankscreen(FALSE);
	blanktime(0);

You wouldn't think asking the screen to go blank would be essential to
unblanking it, but so it goes.  Don't know if this always works, but
it sometimes does.

    Stuart Levy, Geometry Center, University of Minnesota
    slevy@geom.umn.edu