[849] in SIPB bug reports
[celine@ATHENA.MIT.EDU: xscreensaver]
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Wed Jan 17 20:28:17 1990
Date: Wed, 17 Jan 90 20:28:33 -0500
From: Jonathan I. Kamens <jik@PIT-MANAGER.MIT.EDU>
To: celine@ATHENA.MIT.EDU
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: celine@ATHENA.MIT.EDU's message of Tue, 16 Jan 90 21:28:20 -0500 <9001170228.AA24172@W20-575-101.MIT.EDU>
From: celine@ATHENA.MIT.EDU
Date: Tue, 16 Jan 90 21:28:20 -0500
/mit/sipb/${hosttype}bin/xscreensaver -B -v 120 &
I locked my terminal. When I came back, I unlocked it and it died and
printed the following message in my console window.
X Protocol error: not a valid window ID
Major opcode of failed request: 10 (X_UnmapWindow)
Minor opcode of failed request: 0
Resource id in failed request: 0xa00024
Serial number of failed request: 21641
Current serial number in output stream: 21641
Just reporting weirdness, hope the info is useful.
I've been trying to track down the cause of this bug for a while,
with little success. I think it's a race condition bug in the X
server, but I'm not 100% sure, and unfortunately it's difficult to
figure it out without a core dump.
Please do this for me: (1) "unlimit coredumpsize" in your
.environment file, if you don't have it there already; (2)
"xscreensaver.debug: true" in your .Xresources file. This way, when
this same thing happens again, you'll get a core dump in the directory
from which you started xscreensaver, and I'll be able to use it to
help me figure out what's causing the problem. Thanks!
jik
