🚀 go-pugleaf

In article <7q2cuk$9mb$1@dove.qut.edu.au>, Aaron <icelava@bigfoot.com> wrote:
>I can no longer run startx on my machine.  does anybody know how to
>interpret the following error?
>---------------------------------------
...
>_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.

Allan Duncan  a.duncan@trl.telstra.com.au  (+613) 9253 6708, Fax 9253 6776
 Infrastructure - Broadband Networks
 Telstra Research Labs, Box 249 Rosebank MDC
 Clayton, Victoria, 3169, Australia

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.

IceLava wrote:

> what exatly is the role of XFS in the 1st place?  I wish XFree86 had

Not sure about proper documentation ... but, XFS (X Font Server) as the
name implied is a server process that serve fonts :) For example, on a
Solaris box, they have all the dtfonts for CDE, if a Linux box is to
connect to a X session off it, it will have to either install the fonts or
get the fonts off the Solaris' XFS (if it is running one). The second
method save space, save management troubles and avoid replication.