FWIW 0bd3dc0958fa2205aaaa8ebb13e2872b is MD5 of "/usr/share/fonts/truetype/noto". fontconfig keeps one cache file per font directory.
The timestamp of the broken fontconfig cache file is May 15, 10:37. I wonder what my computer was doing at the time. 'last reboot' indicates that I rebooted on May 12, and then today, May 20. I'm pretty sure I launched Chromium right after booting and never quit it until the next reboot. journalctl shows me what my computer was doing on May 15 at 10:36: geg. 15 10:36:59 blynas lxd.daemon[365715]: => Stop reason is: snap refresh geg. 15 10:36:59 blynas lxd.daemon[365715]: => Stopping LXD geg. 15 10:36:59 blynas lxd.daemon[1225]: => LXD exited cleanly so it is snap refresh, not reboot, that creates the broken fontconfig cache file! It's just that when I snap refresh something that is not chromium, I don't restart chromium! -- 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: [snap] color emoji not rendered; many bw emoji rendered as boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
