* Upload proposed patch from upstream bug #103652. If the fontconfig cache
was built on a system that has nanosecond timestamps and then later
transplanted to one that doesn't - for example by mksquashfs as part of a
live CD build - we consider the cache invalid and rebuild it during the
boot process. Depending on the fonts involved, this can take a significant
amount of time and potentially cause knock-on timeouts. The approach in
this patch is to ignore the nanosecond portion of the cache's value if we
get 0 when stat()ing the referenced directory, meaning it is considered
fresh if the rest of the timestamp matches. (LP: #1749546)
This bug was fixed in the package fontconfig - 2.12.6-0ubuntu2
---------------
fontconfig (2.12.6-0ubuntu2) bionic; urgency=medium
* Upload proposed patch from upstream bug #103652. If the fontconfig cache
was built on a system that has nanosecond timestamps and then later
transplanted to one that doesn't - for example by mksquashfs as part of a
live CD build - we consider the cache invalid and rebuild it during the
boot process. Depending on the fonts involved, this can take a significant
amount of time and potentially cause knock-on timeouts. The approach in
this patch is to ignore the nanosecond portion of the cache's value if we
get 0 when stat()ing the referenced directory, meaning it is considered
fresh if the rest of the timestamp matches. (LP: #1749546)
-- Iain Lane <email address hidden> Thu, 05 Apr 2018 17:13:52 +0100