Unfortunately we do not have a clear solution to this yet, so I have unassigned myself from the snapd task and we need more help before we can continue on this. Although, we have a few options as I detail here: https://github.com/snapcore/snapd/pull/8856#issuecomment-644784642
I'm not sure what the best solution is, but definitely this will need some guidance from the desktop team or others more knowledgable about fonts about how to proceed here. Some questions I have include: * Can someone explain the difference between fonts-noto-color-emoji and fonts-kiloji to try and understand why one shows up and the other doesn't with our current fontcache mechanism in snapd? * Can someone explain exactly what things the `dpkg-reconfigure fontcache` command calls to build the cache? is it sufficient to just call fc-cache from the fontconfig package or do we need to be doing something else too? * Would it be possible for the fontcache to be run from inside confinement? I.e. what set of directories from the host would the fontcache binary from the fontconfig package need to see in order to build a fontcache? * If we had to ship fontconfig in the base snaps, is it possible for us to just ship the fontconfig binary like we do today in the snapd snap, or do we really need the full package in order to have full compatibility with all fonts in Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
