Xref: utzoo comp.windows.open-look:54 alt.sys.sun:1991 Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!usc!apple!vsi1!zorch!asgard From: asgard@zorch.SF-Bay.ORG (J.R. Stoner) Newsgroups: comp.windows.open-look,alt.sys.sun Subject: Re: shelltool/cmdtool dumping core Message-ID: <1990Nov11.165348.10554@zorch.SF-Bay.ORG> Date: 11 Nov 90 16:53:48 GMT References: Distribution: comp Organization: Heironamous Botch's Murk Works Lines: 32 In article roberts@studguppy.lanl.gov (Doug Roberts) writes: ;Hi. ;I just finished installing xview2.0 on a Solbourne 5/501 (running ;SunOS 4.0.3 and MIT X11R4), and have encountered the following ;problem: ; ;I right moused in a cmdtool, selected the edit option, and then ;tried to pin the edit menu. This caused the cmdtool/shelltool to core dump. ;The message ; ;"XView warning: Cannot load font '-sun-open look glyph-----*-180-*-*-*-*-*-*' ; (Font package) ;XView error: Unable to fined OPEN LOOK glyph font (Panel package)" ; ;appeared in the console. ;I have _not_ installed OpenWindows, just Xview2.0. ; ;Any ideas on how to fix this? What you have found is something I am rather shocked the MIT dudes have not yet fixed. The problem is in the .bdf file distributed with the MIT release(s). The problem is in the whitespace character in the font name. It seems that the OLGx fonts and all New Century fonts have whitespace characters in the name definition in the BDF file. If you go to the source, change the appropriate line in the file to something like '-' or '_', rerun bdftosnf, install into /usr/lib/X11/fonts/misc (or whereever), then restart the server Xsun will not barf on attempts to load the font. -- J.R. (Use the Source, Luke) Stoner : asgard@zorch.sf-bay.org "Dying is easy, comedy is hard."