[2755] in SIPB bug reports
[jik@pit-manager.MIT.EDU: xscreensaver on the RS/6000]
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Tue Apr 28 16:59:12 1992
Date: Tue, 28 Apr 92 16:58:20 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: bug-sipb@Athena.MIT.EDU
Forgot to CC this to bug-sipb....
----- Forwarded message
Date: Tue, 28 Apr 92 16:53:57 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
Sender: jik@Athena.MIT.EDU
To: jefft@Athena.MIT.EDU
Subject: xscreensaver on the RS/6000
I'm sorry it's taken me so long to get back to you about the problems
you were experiencing with xscreensaver on the RS/6000.
As far as I can tell, the problems were caused by a bug in the x11r4
libraries on the RS/6000. It manifested itself when your lockCommand,
startLocked and displayIcon resources were present, but not when I
removed the lockCommand resource. Since I can't imagine how the
lockCommand resource could possibly affect X in that way, I figure
it's an X race condition bug of some sort.
I recompiled xscreensaver against the X11r5 libraries on the RS/6000,
and the problem appears to have gone away. Please let us know if it
happens again.
jik
----- End of forwarded message
