[2152] in SIPB bug reports

home help back first fref pref prev next nref lref last post

xscreensaver

daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Mon Oct 7 09:40:49 1991

Date: Mon, 7 Oct 91 09:40:13 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: ckclark@mit.edu
Cc: bug-sipb@Athena.MIT.EDU
In-Reply-To: Calvin Clark's message of Mon, 7 Oct 91 01:24:08 -0400 <9110070524.AA11900@podge>

   Date: Mon, 7 Oct 91 01:24:08 -0400
   From: Calvin Clark <ckclark@Athena.MIT.EDU>
   Reply-To: ckclark@mit.edu

   (The current xscreensaver installed in /mit/sipb/vaxbin is the same as in
   the build tree.)

   A user came into the office about a half hour ago, and his xscreensaver
   was frozen, not accepting any input from the mouse or keyboard.  It was
   also not accepting any remote connections (e.g., using xfree or
   telnetting to appropriate port).  The screensaver was in a state where
   it was prompting for the password.  The machine had to be rebooted, as
   there was no way to kill the screensaver remotely.

   The workstation was a VS/2000.

I cannot duplicate this behavior.  The next time it happens, please
try to get more information from the person reporting it, including:

1. Username.
2. Any X resources loaded (xscreensaver or generic)?
3. How long had the xscreensaver been running?
4. Did it hang the first time the screen was locked, or a subsequent
   line?
5. Did he lock the screen by selecting the "Lock screen" menu item or
   by setting "Auto lock" and clicking on the xscreensaver button?
6. Can this be duplicated?

  jik



home help back first fref pref prev next nref lref last post