Path: utzoo!attcan!uunet!decwrl!wuarchive!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!eru!hagbard!sunic!mcsun!unido!pbinfo!pbinfo-n!x-window From: x-window@uni-paderborn.de (X-Window Betreuung) Newsgroups: comp.windows.x Subject: Re: Strange new xset error Message-ID: Date: 9 Oct 90 11:55:17 GMT References: Sender: news@uni-paderborn.de (News Uni-Paderborn) Distribution: comp Organization: Uni Paderborn FB 17 Informatik GERMANY Lines: 24 In-Reply-To: hogan@csl.sri.com's message of 8 Oct 90 21:20:14 GMT In article 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 * <----