SUMMARY: dtlogin / xset / bad font path element

All respondents suggested reading the manual page for xset :-) 

Subsequent events suggest that the xset warnings were not the cause of the
dtlogin problem described.  A short time after I sent the original message
to sunmanagers dtlogin crashed; when restarted the login problem had gone
away.  It's possible that there is a bug in dtlogin's child management
(suggested by the "Warning: Null child found in argument list to unmanage"
message immediately followed by a segmentation violation error.)

Thanks to all who supplied suggestions. I include Noel Hunt's message below
as it's of general interest to anyone with font problems...

"But to find out what's in your font path, use `xset q'. Several sections of
data are output. The font path is towards the end. This will be a series of
directory names separated by commas:

Font Path:
  /usr/openwin/lib/X11/fonts/F3/,/usr/openwin/lib/X11/fonts/F3bitmaps/,/usr/openwin/lib/X11/fonts/Type1/,/usr/openwin/lib/X11/fonts/Speedo/,/usr/openwin/lib/X11/fonts/misc/,/usr/openwin/lib/X11/fonts/75dpi/,/usr/openwin/lib/X11/fonts/100dpi/,/home/nhunt/lib/X11/fonts/pcf/,/usr/openwin/lib/locale/ja/X11/fonts/75dpi/,/usr/openwin/lib/locale/ja/X11/fonts/F3/,/usr/openwin/lib/locale/ja/X11/fonts/F3bitmaps/,/usr/openwin/lib/locale/ja/X11/fonts/TT/,/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps,/usr/openwin/lib/locale/sun_eu_greek/X11/fonts/TrueType/,/usr/openwin/lib/locale/iso_8859_9/X11/fonts/Type1/,/usr/openwin/lib/locale/iso_8859_8/X11/fonts/Type1/,/usr/openwin/lib/locale/iso_8859_8/X11/fonts/TrueType/,/usr/openwin/lib/locale/iso_8859_7/X11/fonts/Type1/,/usr/openwin/lib/locale/iso_8859_5/X11/fonts/Type1/,/usr/openwin/lib/locale/iso_8859_4/X11/fonts/Type1/,/usr/openwin/lib/locale/iso_8859_2/X11/fonts/Type1/,/usr/openwin/lib/locale/iso_8859_15/X11/fonts/TrueType/,/usr/openwin/lib/!
locale/iso_8859_13/X11/fonts/Type1/,/usr/openwin/lib/locale/iso_8859_13/X11/fonts/TrueType/,/usr/java1.2/jre/lib/fonts/,/opt/SUNWns6/java/lib/fonts/

You have not have so many, that isn't important. Each directory
though has to be `well-formed' in an X11 font sense. Each directory
must contain a file `fonts.dir'; it may also have `fonts.alias'.
These of course have to be constructed correctly. If its not
obvious which directory is causing problems, I suppose you could
strip the path down and add elements back one by one with
`xset fp+ dir/' (trailing /)."





Original message....


On a Sol8 system, dtlogin has started to misbehave and will not accept new
logins -- attempts to login to CDE return to the login screen or the
network connection is terminated.

In /var/dt/Xerrors I have multiple entries like...

/usr/openwin/bin/xset:  bad font path element (#37), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
Warning: Null child found in argument list to unmanage
dtlogin: received signal 11

Ok, how do I find the "bad font path element" and fix it?  Where are the
clues that tell me which directories or config files to look in and what am
I looking for?



-- 
/\ Geoff. Lane. /\ Manchester Computing /\ Manchester /\ M13 9PL /\ England /\
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers