Menu

#42 fonts not installed

v1.0_(example)
open
nobody
None
2
2017-09-08
2017-03-27
No

Although the installer offers "Fonts" with a preset checkbox, and I did not uncheck it, it did not install any decent fonts.

xlsfonts.exe
-misc-fixed-medium-r-semicondensed--0-0-75-75-c-0-iso8859-1
-misc-fixed-medium-r-semicondensed--13-100-100-100-c-60-iso8859-1
-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
6x13
cursor
fixed

Discussion

  • David Wojtowicz

    David Wojtowicz - 2017-06-09

    This seems to be a regression in v1.19.2. The font path is not automatically populated with the fonts that are installed. The font path can be manually appended using the xset command, but this setting would need to be reapplied each time the server is started.

    If you go back to version v1.18.3 the problem does not exist.

     
  • Peter Sobisch

    Peter Sobisch - 2017-08-15

    Hello David,

    I have the same problem, but i cant use 1.18 because it crashes when i start firefox. 1.19 does not crash but it provides only one font ("fixed"). Therefore I have to go with 1.19.
    Is there any other workaround for 1.19.2 without re-aplying xset?
    As I know there a 2 different ways to tell the fonts location to the VcXsrv:
    1) command line: -fp "path"
    2) xset fp= "path1","path2"

    The first seems to be fine as a workaround, but it works only for one path, I can't add all of the missing paths on command line.
    The second one would need to start the VcXsrv on the Windows host first, then on the linux machine xset need to be fired with all those missing font directories (here I can give more than one directory), but, we have several different Xserver on different Windows machines and I will not changing font path on an other Xserver than VcXsrv which points to VcXsrv.

    So I'm looking a workaround which would run on the same host where VcXsrv is running, i could imaging to start a wrapper script and doing the right things. but what?

     

    Last edit: Peter Sobisch 2017-08-15
  • Werner Henze

    Werner Henze - 2017-09-08

    Same problem with 1.19.3.0.

     

Log in to post a comment.