🚀 go-pugleaf

With an Indigo R3000 Elan running 4.0.5F:

I've had problems when using the powerflip / SGI logo combination as the
screen saver.  Occasionally, this program hangs and I have to reset
the graphics system.  After describing my woes to the hot line (sorry,
I guess that's an old name?), I've gotten two new graphics boards and
one new CPU board.

Since the new CPU board (most recent change), it has not yet hung the
graphics system, but it only happened sporadically anyway.

Today, I wanted to let it run overnight by starting it from
my toolchest.  The line in the toolchest is

    "SGI Logo"          f.checkexpr "test -x /usr/sbin/haven -a -x /usr/demos/bin/powerflip -a -r /usr/demos/data/yaodl/logo.ydl" "/usr/sbin/haven /usr/demos/bin/powerflip -z /usr/demos/data/yaodl/logo.ydl"

But instead of the logo appearing for a moment (right after I choose
that entry from the toolchest) and then going away, a window occupying
about 95% of the screen stays there.  (This window, except for not
occupying the whole screen, looks like what one expects to see when
this screen saver is in operation.)  In /usr/adm/SYSLOG I find

Jan 11 16:52:55 axe Xsession: zsd: X Error of failed request:  BadWindow (invalid Window parameter)
Jan 11 16:52:55 axe Xsession: zsd:   Major opcode of failed request:  20 (X_GetProperty)
Jan 11 16:52:55 axe Xsession: zsd:   Resource id in failed request:  0x34
Jan 11 16:52:55 axe Xsession: zsd:   Serial number of failed request:  160
Jan 11 16:52:55 axe Xsession: zsd:   Current serial number in output stream:  160

Can anyone shed some light on why this is happening?  In previous
cases, logging out and in again fixes (temporarily) this problem.
But what is causing this problem?  Should I ask for a new backplane?
Maybe a new power supply?  ("Collect the whole set.")

Thanks.

			Jim Diamond
			zsd@axe.drea.dnd.ca