Installer should copy fontconfig cache to the installed system

Bug #1824770 reported by Paweł Stołowski
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Incomplete
Undecided
Unassigned
snapd (Ubuntu)
Incomplete
Undecided
Unassigned
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

After the installation completes, fontconfig cache files (/var/cache/fontconfig) should be copied from the live CD session to the just installed system, before reboot.

The rationale:

Snapd creates fontconfig cache files (/var/cache/fontconfig) for fontconfig cache format v6 and v7 (this is done by snapd to significantly reduce startup time for snaps that may use one of the two formats). This is a one-time operation that can take as much as ~20 seconds; it's performed on the live CD session as it runs snapd, but since the newly installed system has empty /var/cache/fontconfig after first boot, it needs to be repeated by snapd. This affects first boot experience as it has impact on readiness of snapd and snap for normal usage. Observed with 19.04 installs.

Revision history for this message
Michael Vogt (mvo) wrote :

Is there anything that snapd needs to do here? It already generates the caches, does it need to do more? It seems this is a ubiquity task, yes?

Changed in snapd:
status: New → Incomplete
Changed in snapd (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.