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 Hanno Foest <hurga-x...@tigress.com> schrieb am Sa., 19. Feb. 2022, 01:29: > Hi, > > after setting up a new remote x2go instance (using Devuan) I noticed > that xterm complained > > xterm: cannot load font > "-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1" > > I traced the issue to the font path (displayed with xset q) missing > /usr/share/fonts/X11/misc, so I added it with > > xset +fp /usr/share/fonts/X11/misc > > and things started behaving normally again. - But: Where is the font path > in x2go actually being set? I'm not sure if some autoconfiguration > failed, or if it's a compile time issue, or something else. - For the > same issue there's a bug report in Ubuntu, see > > https://bugs.launchpad.net/ubuntu/+source/x2goserver/+bug/1891825 > > and especially the remark about the man page at the end. > > Hanno > > _______________________________________________ > x2go-user mailing list > x2go-user@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user >
_______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
