Curiously, fc-cat /var/cache/fontconfig/0bd3dc0958fa2205aaaa8ebb13e2872b-le64.cache-7.bork does not complain about the cache file being invalid. It shows information about a bunch of Noto fonts BUT! not the ColorEmoji one!
shows that NotoColorEmoji.ttf is the only font missing from the font cache file.
Now it's time for baseless speculation: could it be that snap refresh somehow runs fc-cache inside a container where /var/cache/fontconfig is bind-mounted from the host OS, but /usr/share/fonts/truetype/ comes from some base snap image?
Curiously, fc-cat /var/cache/ fontconfig/ 0bd3dc0958fa220 5aaaa8ebb13e287 2b-le64. cache-7. bork does not complain about the cache file being invalid. It shows information about a bunch of Noto fonts BUT! not the ColorEmoji one!
diff -u <(fc-cat /var/cache/ fontconfig/ *.bork| cut -d'"' -f2|sort) <(ls /usr/share/ fonts/truetype/ noto/|sort)
shows that NotoColorEmoji.ttf is the only font missing from the font cache file.
Now it's time for baseless speculation: could it be that snap refresh somehow runs fc-cache inside a container where /var/cache/ fontconfig is bind-mounted from the host OS, but /usr/share/ fonts/truetype/ comes from some base snap image?