Comment 5 for bug 1856624

I can confirm that the bug described in the askubuntu.com link above is the bug I'm seeing; the workaround stated there (renaming `~/.fonts`) was enough to prevent it occurring.

I have fontconfig 2.12.6-0ubuntu2 installed (and my fontconfig-config is the same version).

Should this bug report be moved to the fontconfig package, as apparently it's the underlying cause of the bug? Presumably it will be fixed if/when Ubuntu updates to a newer version of fontconfig.