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
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-x2go@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
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
-
Hanno Foest -
Ulrich Sibiller