Ulrich Sibiller <uli42@gmx.de> wrote on Sun, 31 Mar 2019 11:59:24 +0200:
Alright, the problem then is that Linux From Scratch is using fontpaths that differ from the default ones.
My font paths may not be pure Linux From Scratch, so don't bother changing any font path settings in your sources.
Actually, /usr/share/fonts is the default location of fonts in fontconfig and LFS sets a link for TTF fonts (ln -s $XORG_PREFIX/share/fonts/X11/TTF /usr/share/fonts/X11-TTF). I decided to put *all* my fonts directly into /usr/share/fonts. So that's actually not pure LFS.
Can you please send us the correct list (derived from the defaults I posted earlier) for your distribution?
Okay, I've started completely from defaults again. Here is what I had to do in order to make my special font (actually two of them, one for xterm and one for xdosemu) working.
Adding my non-default (non-LFS) font paths to the script that starts the session on the Linux PC (for nxagent):
xset fp /usr/share/fonts/75dpi/,/usr/share/fonts/misc/,built-ins
I totally get now why this is necessary.
Copying my /usr/share/fonts/{75dpi,misc} to the x2go Windows client to C:\Program Files\x2goclient\VcXsrv\fonts\{75dpi,misc}.
I still don't get why *this* is necessary, but it is. Without copying it doesn't work. (Actually, without copying, xterm seems to use my font, but its window is far too small and glyphs are overlapping; xdosemu wouldn't use my font at all.)
Because the Windows path in 2. is default for VcXsrv, I did *NOT* to have to change VcXsrv's default command line options (as stated previously). It is sufficient to select "use integrated X-Server" (with all its defaults).
One other thing:
Apparently, C:\Program Files\x2goclient is the default installation directory for the Windows client. On the contrary, the fixed path "C:\\program files\\vcxsrv\\vcxsrv.exe" is used three times in the client source. So when you'd change to "use custom X-Server" and don't watch out for the default executable put in there, you're screwed. The client immediately shuts down with an error at start-up then.
That should be it. Thank you for your support.
Ingo