[2835] in SIPB bug reports
xscreensaver on the rios dieing
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Thu May 14 16:58:09 1992
Date: Thu, 14 May 92 16:57:44 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: jefft@Athena.MIT.EDU
Cc: bug-sipb@Athena.MIT.EDU
In-Reply-To: Jeff Tang's message of Thu, 07 May 92 04:44:34 EDT <9205070844.AA09288@air-traffic-controller.MIT.EDU>
From: Jeff Tang <jefft@Athena.MIT.EDU>
Date: Thu, 07 May 92 04:44:34 EDT
Sender: jefft@Athena.MIT.EDU
Twice tonight, I ran xscreensaver on the rios and it died after 30
minutes. Here are the error messages:
21:48 X Error of failed request: BadName (named color or font does not exist)
22:40 Major opcode of failed request: 45 (X_OpenFont)
22:40 Serial number of failed request: 738
22:40 Current serial number in output stream: 735
00:26 X Error of failed request: BadName (named color or font does not exist)
00:26 Major opcode of failed request: 45 (X_OpenFont)
00:26 Serial number of failed request: 815
00:26 Current serial number in output stream: 812
After much investigation, I have concluded with glee that this is due
to yet another bug in the RS/6000 X server.
It seems that despite the fact that XLoadQueryFont's specification
says that it should return NULL when the named font does not exist,
the RS/6000 X server has decided that *sometimes* it should generate a
BadName error in response to this condition. The circumstances in
which this occurs do seem to be somewhat questionable, but it has
something to do with the lockCommand X resource, I think.
I've worked around the problem by changing the name of the font that
the logout button uses in the application defaults file, so that it
exists on all of our platforms.
Sigh.
jik
