I come to the conclusion that it must be a Catalina problem with X11 fonts (directory access rights or something in that direction).
When I run the program bsvc locally under macOS (catalina 15.5.6) the application starts and has no font problem at all. It seems to be a problem with the remote client accessing the X11-server. — Christoph > Am 22.08.2020 um 11:23 schrieb Peter West <li...@pbw.id.au>: > > On my Mojave installation, there’s am MS Reference Sans Serif. > > >> On 22 Aug 2020, at 6:32 pm, Andrew Udvare <audv...@gmail.com >> <mailto:audv...@gmail.com>> wrote: >> >> >> >> On Sat, Aug 22, 2020, 02:37 Christoph Kukulies <k...@kukulies.org >> <mailto:k...@kukulies.org>> wrote: >> I’m running a tk/tcl app on my FreeBSD box that has the font „MS Sans Serif“ >> wired in. >> This leads to an X11-error when starting the application (bsvc) with my >> macOS (catalina 15.5.6) as the server: >> >> $ bsvc >> X Error of failed request: BadName (named color or font does not exist) >> Major opcode of failed request: 45 (X_OpenFont) >> Serial number of failed request: 42 >> Current serial number in output stream: 59 >> >> >> Is there a way to install the missing font using a macport? Or what is the >> closest standard X11 font that can be used instead of the MS font? >> >> That font should be included with macOS as it has been since Leopard. It's >> possibly named slightly differently. >> >> The closest font is probably Helvetica but your app has the MS font hard >> coded. >> >> — >> Christoph >> >> >> >
smime.p7s
Description: S/MIME cryptographic signature
