Yeah, I’m pretty sure that @xitian is right that those errors are due to the Fontconfig version mismatch (Debian 9 is running Fontconfig 2.11 and doesn’t encounter this issue).
My only other thoughts are really just throwing spaghetti against the wall:
-
On my system I have to set
home.sessionVariables.LOCALE_ARCHIVE = "${pkgs.glibcLocales}/lib/locale/locale-archive";to work around locale errors (which screw up some of the terminal apps I use). I don’t think this would be causing your problem, though it should get rid of the first warning in @NobbZ’s output. -
I’ve found it virtually impossible to get all of the environment set up by home-manager to be respected by Chrome OS’s launchers, and thus have resorted to changing all of my GUI app
Exec=lines toExec=bash -le $APP. However, temporarily reverting this change doesn’t mess up my fonts, so it’s probably also not the solution.
Having had the opportunity to test things out on my work system now, I can see that fonts.fontconfig.enable = true; was a red herring… Disabling results in my GUI apps not being able to find the fonts I’ve installed via home-manager, but doesn’t actually produce the tofu you’re describing.