bph@buengc.BU.EDU (Blair P. Houghton) (10/04/89)
Using default setups, having changed nothing on the server or in
any of the X applications recently, we now get the following for
some applications:
Cannot open font file <*>
Where <*> is any of a number of perfectly available, previously
usable fonts. Nothing has changed, but suddenly nothing works.
These error messages are dumped by the kilobyte into the X0msgs file in
.../adm. It gets huge in a short period of time. Something in the
server (is it in the server or in the application? I don't know, and I
can't tell from looking.[1]) is writing the message for several different
fonts that the application requests, and then seems to go into an
infinite loop on one of them.
There is nothing wrong with the fonts. I can get them to come
on-screen using xfd, but not with the offensive applications.
Munging the font paths has nothing to do with it.
Everyone has read _and_ execute permission on the font files.
The only way it could really fail to open them is if it wanted
to write to them as well...
This only happens to some users, and only on certain machines,
and started happening only recently.
If it's a difference in the resources or in the environment, we
can't identify a keyword that could be the culprit.
The hardware is a uVAX II/GPX, the system is Ultrix 3.1, UWS 2.1,
and the program doing the wrong thing is vem.
--Blair
"You coulda guessed that last part."
[1] Why would a client be writing into the server's log file??madd@bu-cs.BU.EDU (Jim Frost) (10/04/89)
In article <4427@buengc.BU.EDU> bph@buengc.bu.edu (Blair P. Houghton) writes: |Using default setups, having changed nothing on the server or in |any of the X applications recently, we now get the following for |some applications: | | Cannot open font file <*> What I would suggest is walking over to a Sun (there are several on campus :-) and seeing if the Sun server exhibits the same problem (do the messages still show up on the client's logfile?). If so, it's a client problem, if not, it's a server problem. Since you say xfd works, I rather expect it's a result of the application. jim frost software tool & die madd@std.com