[308] in SIPB bug reports
new-xscreensaver (RT)
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Tue Feb 7 16:01:57 1989
Date: Tue, 7 Feb 89 16:01:50 EST
From: Jonathan I. Kamens <jik@Athena.MIT.EDU>
To: raeburn@ATHENA.MIT.EDU
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: Ken Raeburn's message of Tue, 7 Feb 89 15:55:00 EST <8902072055.AA04979@PROMETHEUS.MIT.EDU>
Date: Tue, 7 Feb 89 15:55:00 EST
From: Ken Raeburn <raeburn@ATHENA.MIT.EDU>
Date: Tue, 7 Feb 89 10:14:11 EST
From: Jonathan I. Kamens <jik@ATHENA.MIT.EDU>
Not considered a bug, but rather a missing feature.
It is sometimes possible to get into a state where although screen 0
is ``locked,'' typed input (supposedly to the password prompt) goes to
a window in screen 1. I haven't tried it with the new screensaver,
but I would claim that this is indeed a bug.
You're right -- when I grab the pointer I should constrain it to the
xscreensaver window so the user can't roll the mouse onto screen 1
without realizing it.
It will be fixed....
jik
