[Bug 2061995] Re: ULLTS 22, 24: FontConfig broken by including ".conf" file

[Peter Grandi]

** Also affects: fontconfig (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2061995

Title:
  ULLTS 22,24: FontConfig broken by including ".conf" file

Status in Ubuntu:
  New
Status in fontconfig package in Ubuntu:
  New

Bug description:
  This happens to me on both ULTS 22 and ULKTS 24 on FotnConfig in
  somewhat different ways:

  * In ULTS 24 if there is a file '/etc/fonts/local.conf' then all fonts
  are rendered as if the font were not hinted or 'hinting' were 'false'.
  This is not noticeable if antialiasing is on, and most users default
  to antialiasing.

  * In ULTS 22 if there is a file
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' then some fonts are no longer
  found, or get rendered with rectangular shapes. I guess not many users
  customize their font settings.

  A telling example from ULTS 22:

  $  cat /etc/fonts/conf.d/10-antialias.conf
  <?xml version="1.0"?>
  <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
  <fontconfig>
  <!--  Use the Antialiasing -->
    <match target="pattern">
      <edit name="antialias" mode="append"><bool>false</bool></edit>
    </match>
  </fontconfig>
  $  cp -p /etc/fonts/conf.d/10-antialias.conf $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  This happens also with a skeleton
  '$XDG_CONFIG_HOME/fontconfig/fonts.conf' (or '/etc/fonts/local.conf')
  too:

  $  cat > $XDG_CONFIG_HOME/fontconfig/fonts.conf
  <?xml version="1.0"?>
  <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
  <fontconfig>
  </fontconfig>
  $  fc-list 'dejavu sans mono' family
  $  rm $XDG_CONFIG_HOME/fontconfig/fonts.conf
  $  fc-list 'dejavu sans mono' family
  DejaVu Sans Mono

  None of these anomalies happen under ULST 20.

  My impression: symptoms vary and are weird, so probably it is
  something like a buffer overflow when reading the ".conf" files or the
  use of not-initialized memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2061995/+subscriptions