I got it partially figured out... in my old x2go instance, there's a symlink from /usr/share/nx/fonts to /usr/share/fonts/X11, and creating it in the new install made the font path change from
/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/75dpi,/usr/share/fonts/X11/100dpi,built-ins
to
/usr/share/nx/fonts/misc/,/usr/share/nx/fonts/Type1/,/usr/share/nx/fonts/75dpi/,/usr/share/nx/fonts/100dpi/,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/75dpi,/usr/share/fonts/X11/100dpi,/usr/share/nx/fonts/Type1,/usr/share/nx/fonts/75dpi,/usr/share/nx/fonts/100dpi,built-ins
which then contains the fonts xterm complained about missing.
Still, this is undocumented, and I'm not sure why the symlink was missing, so I'll open a bug as you suggested.
Hanno
On Sat, Feb 19, 2022 at 10:29:49AM +0100, Ulrich Sibiller wrote:
The font paths are mostly hardcoded into nx-libs (NX agent, to be precise). I am not sure if x2go is setting them explicitly but I doubt it. Have to check. Adding another font path to nx-libs is no big deal but I agree that x2go could/should also do this. So may I ask you to open a bug report at GitHub.com arcticaproject nx-libs? Thanks, Uli