[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Xvnc giving errors after kernel upgrade



grey@dmiyu.org wrote:
> Chris Howie said:
>>Fatal server error:
>>could not open default font 'fixed'
>
>     Well, obvious question; is the fixed font somewhere on your system?  If
> so, can Xvnc find it?  I mean if the server's giving a clear indication
> of the problem like that it would be the first place to look.  :D

Yes, fixed exists in that path -- I have it when using X.org, after all.
Perhaps of more interest is:

Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing
from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!

Meaning, in all probably, Xvnc has just emptied its font path list.  But why?
And why would a kernel upgrade cause this?

-- 
Chris Howie
http://www.chrishowie.com

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/IT d-(--) s:- a--->? C++(+++)$> UL++++ P++++$ L+++>++++ E---
W++ N o++ K? w--$ O M- V- PS--(---) PE++ Y+ PGP++ t+ 5? X-
R(+)>- tv-(--) b- DI+> D++ G>+++ e>++ h(--)>--- !r>+++ y->+++
------END GEEK CODE BLOCK------

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: