[753] in SIPB bug reports
xscreensaver bug?
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Mon Nov 20 18:07:59 1989
Date: Mon, 20 Nov 89 18:07:42 -0500
From: Jonathan I. Kamens <jik@PIT-MANAGER.MIT.EDU>
To: bjaspan@ATHENA.MIT.EDU
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: Barr3y Jaspan's message of Sun, 19 Nov 89 15:45:45 -0500 <8911192045.AA05613@STEVE-DALLAS.MIT.EDU>
Take a look at the code in savescreen.c in the xscreensaver sources.
I have repeatedly modified the code that grabs the keyboard and mouse,
up to the point where it is incredibly paranoid about making sure that
the grabs succeed, and won't even lock the screen if they do not. And
yet the screen gets locked anyway....
In other words I just don't know what's happening, and I don't know
how to fix it. I would really appreciate any input into what might be
causing the problem.
I'm going to try a couple other changes that might help to isolate
the problem; I'll install them tonight, so they'll go out tomorrow
when the packs get released. We'll see if this solves the problem.
One final note: I've noticed that this probably occurs almost
exclusively on the VAX 3100's, not on other VAXen. Was that the case
in the two incidents you recorded? If so, we might have to consider
what it is about the 3100 that causes the problem to manifest itself.
Perhaps the problem is that the 3100 goes too fast? (1/2 :-)
jik
