We're a bit behind when it comes to fontconfig versions. That means we won't load the system provided cache files on startup and will have to spend a lot of time generating our own. We should look at upgrading to something more recent.
Hopefully it will also get rid of this noise from tlclient: Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 78: saw unknown, expected number
ThinLinc builds against fontconfig 2.10.1 which was release 2012-07-27 latest version is 2.13.1 release 2018-08-30 and there has been 24 stable releases in between.
(In reply to comment #2) > ThinLinc builds against fontconfig 2.10.1 which was release 2012-07-27 > latest version is 2.13.1 release 2018-08-30 and there has been 24 stable > releases in between. > I tested to upgraded fontconfig to version 2.13.1 in our build system and rebuilt the client and server. Running the client, the 55 rows of Fontconfig warnings in the logfile has disappear and the system fontconfig cache version 7 is used instead of generating a new one. - RHEL 6 uses fontconfig v2.8.0, cache version 3 - Ubunru 16.04 uses fontconfig v2.11.94, cache version 6 - RHEL 7, Fedora 28 uses fontconfig v2.13.0, cache version 7
(In reply to comment #3) > (In reply to comment #2) > > Running the client, the 55 rows of Fontconfig warnings in the logfile has > disappear and the system fontconfig cache version 7 is used instead of > generating a new one. > The sames goes for the server build, fontconfig warnings are gone from xinit.log.
(In reply to comment #3) > I tested to upgraded fontconfig to version 2.13.1 in our build system and > rebuilt the client and server. > > Running the client, the 55 rows of Fontconfig warnings in the logfile has > disappear and the system fontconfig cache version 7 is used instead of > generating a new one. > Testing on RHEL 6 shows following errors: Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 23: Having multiple <family> in <alias> isn't supported and may not work as expected the format is: <alias> <family></family> <family></family> . . </alias> The new format looks like this: <alias> <family></family> </alias> <alias> <family></family> </alias> This suggests that aliases would be restricted into one alias when running on an old fontconfig system. Theoretically this would mean if we some were uses a font alias it could faild. However it looks all good with components that links statically against our fontconfig; openbox, tlclient etc. have.
Commit r33948 fixes CBLINK static libraries for vnc-shadow-notify
Tested 32-bit and 64-bit tlclient and vncviewer on Fedora 28 and RHEL 6. Tested 64-bit tlclient and vncviewer on Ubuntu 18.04. Tested 64-bit pdf2ps on Fedora 28 (not sure when it uses fontconfig though) Tested tlclient and vncviewer on the ARM terminal. No issues found except some expected warnings to stderr on RHEL 6 and the ARM machine. Tested openbox and vnc-shadow-notify on Ubuntu 18.04, RHEL 6 and Fedora Rawhide.
