HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

font server type1 not starting

 
Bernward
Occasional Visitor

font server type1 not starting

when starting the xfs with default configuration I get the errors:

xfs error: Warning: Rasterizer "/usr/lib/X11/fs/ufstrast.sl" could not be loaded: Invalid argument

xfs error: Warning: Rasterizer "/usr/lib/X11/fs/iforast.sl" could not be loaded: Invalid argument

But I can't get any information about paarmeters for these rasterizers

2 REPLIES

Re: font server type1 not starting

>xfs error: Warning: Rasterizer "/usr/lib/X11/fs/ufstrast.sl" could not be loaded: Invalid argument

 

This is most likely EINVAL, an argument to a syscall.  You might be able to use tusc(1m) to track it down.

ranganath ramachandra
Esteemed Contributor

Re: font server type1 not starting

The "could not be loaded" in the message seems to imply that xfs is trying to explicitly load this shared library (".sl").
First, check with the "file" command whether the shared library file exists and is of the right architecture (PA-RISC or IA64) and bit width (32-bit or 64-bit) - they should all match the xfs executable.  If there is a mismatch, you need to fix that.

I could find this file only on a PA-RISC system.

[ ranga ] $ file /usr/lib/X11/fs/ufstrast.sl
/usr/lib/X11/fs/ufstrast.sl:    PA-RISC1.1 shared library -not stripped
[ ranga ] $ file /usr/bin/X11/xfs
/usr/bin/X11/xfs:       PA-RISC1.1 shared executable dynamically linked -not stripped dynamically linked


On HP-UX, a shared library can be loaded explicitly using either dlopen(3C) or shl_load(3X).

[ ranga ] $ ldd -y,shl_load /usr/bin/X11/xfs
  :
  shl_load (code) : needed by /usr/bin/X11/xfs; found in /usr/lib/libdld.2

No such "needed" found for dlopen, though.
So, looking at the shl_load(3X) man page:

[EINVAL]       The specified handle or index is not valid or an
               attempt was made to load a library at an invalid
               address.

That does not look helpful - shl_load does not need handle or index to be specified. Perhaps the man page does not cover all the cases for which shl_load would return EINVAL; shl_load will leave the value of errno as set by the last system call. So, as Dennis suggests the next step is to identify which system call set errno to EINVAL.