[comp.windows.x] Strange new xset error

hogan@csl.sri.com (Emmett Hogan) (10/09/90)

We have suddenly started getting an error whenever we try to change
the font path using xset, and for the life of me, I cannot figure out
what could have changed to induce this error. It happens on Sun 3
machines running SunOS4.0.3 and X11R4 (patch level 14) as well as
SPARCstation 1+'s running SUNOS 4.1 and X11R4 (patch level 18).  Here
is the error:

> xset fp+ /homes/hogan/fonts
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  51 (X_SetFontPath)
  Minor opcode of failed request:  0
  Resource id in failed request:  0x3
  Serial number of failed request:  4
  Current serial number in output stream:  6

The other xset commands work, just fp blows up.  Anybody have any idea
what could cause this...I'm stuck.

Thanks in advance,
Emmett


--
-------------------------------------------------------------------
Emmett Hogan              Computer Science Lab, SRI International
Inet: hogan@csl.sri.com
UUCP: {ames, decwrl, pyramid, sun}!fernwood!hercules!hogan
USMAIL: BN179, 333 Ravenswood Ave, Menlo Park, CA  94025
PacBell: (415)859-3232 (voice), (415)859-2844 (fax)
ICBM: 37d 27' 14" North, 122d 10' 52" West
-------------------------------------------------------------------

x-window@uni-paderborn.de (X-Window Betreuung) (10/09/90)

In article <HOGAN.90Oct8142014@trollope.csl.sri.com> hogan@csl.sri.com (Emmett Hogan) writes:

   > xset fp+ /homes/hogan/fonts
   X Error of failed request:  BadValue (integer parameter out of range for operation)
     Major opcode of failed request:  51 (X_SetFontPath)
     Minor opcode of failed request:  0
     Resource id in failed request:  0x3
     Serial number of failed request:  4
     Current serial number in output stream:  6

   The other xset commands work, just fp blows up.  Anybody have any idea
   what could cause this...I'm stuck.

   Thanks in advance,
   Emmett

Perhaps you forgot mkfontdir /homes/hogan/fonts. I had this problem a
few months ago, and I believe --- modulo bad memory --- that this was
the reason of the problem. 

Hope this helps
Swen

---->  Swen Thuemmler  *  X-Betreuung  *  <swen@uni-paderborn.de>  <----

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (10/09/90)

This should mean one of your font directories has a bad/missing/unreadable
fonts.dir or a bad/unreadable fonts.alias file.  The value given in the
error message for "Resource id in failed request" is the index (from zero)
into the font path of the bad directory.