🚀 go-pugleaf

Based on the advice given by someone else to solve the Netscape Java
crash problem, I did a chkfontpath command to add another font into the
list.  Netscape no longer crashes, but I couldn't startx anymore bcoz of
that.

I was subsequently adviced to comment the default font path unix/:-1
line in XF86Config to force X server to use other fonts (what fonts???
it still loox the same).  It got X started up again, but now it seems I
can't use wallpapers in AfterStep.

what exatly is the role of XFS in the 1st place?  I wish XFree86 had
written some proper doc stating clearly how their components integrate
their functions to work together.  They did write program descriptions
like these, didn't they??


Allan Duncan wrote:
> 
> ...
> >_FontTransSocketUNIXConnect: Can't connect: errno = 111
> >failed to set default font path 'unix/:-1'
> >Fatal server error:
> >could not open default font 'fixed'
> 
> You didn't say what you had been doing prior to this happening.
> 
> I had the same fault after I rebuilt my system from one drive to
> another, changing partition sizes as I went.  Since I had the old
> (functioning) drive and the new, I played around with fstab switching
> partitions between the old and new and found that xfs died on the new
> /tmp partition, at which time I noticed the permissions were wrong -
> there must be a 't' at the end.
> 
> chmod brought xfs back to life.  Why it wants to write program text to
> /tmp I don't know, or more importantly does it _need_ to.