Strange behavior with web PDFs

It should have the permissions as set as in the OS install. At the OS install moment it should be created with standard options. If it’s there (default place) an you have not moved it for your session (set a new one in $FONTCONFIG_PATH) I don’t know why your PDF reader in your browser is claiming “Fontconfig error: Cannot load default config file” unless its reading permissions are denied. You can assure its readable by all with

chmod a+r /etc/fonts/fonts.conf

But I don’t really know if this is your problem here. It would be interesting to see the output of

ls -al /etc/fonts/fonts.conf

before adding the global reading capability using that chmod.

Looks like the permissions were already set.

That’s why I do prefer Ubuntu / Debian options. Never got caught with weird unexplained things with them.

1 Like

I have seen differences between FireFox and Chrome - found this out the hard way with key milestone demo failing for client bc laptop had different browsers than home box and had to remote connect to home box to get demo to work :sweat_smile:

So yeah, definitely try on multiple browsers. So far, FireFox has given me fewer issues.