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 <>  Thu, 05 Apr 2018 17:13:52

** Changed in: fontconfig (Ubuntu Bionic)
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.

  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
Status in fontconfig package in Ubuntu:
  Fix Released
Status in fontconfig source package in Bionic:
  Fix Released

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
   PATH=(custom, no user)
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to