GNOME Bugzilla – Bug 585455
Allow disabling font monitoring
Last modified: 2015-11-04 08:58:47 UTC
By checking FcConfigGetRescanInterval(). If rescanning is not requested, we wouldn't send notifications. To be able to start monitoring again, we have to keep monitoring the config files still. So this may not fully fix bug 559168. Another option is to also add a gconf key.
For this to be effective, one would just not monitor any font directory. gconf key would be more effective. Though ultimately some sort of cache for /etc/mnttab if can be address by 559168 is the proper solution.
Behdad, with the fix to http://bugzilla.gnome.org/show_bug.cgi?id=585360 I don't think this bug is necessary.
This is a separate issue and I like to fix it eventually.
I don't understand in which cases this would be useful. We override the fontconfig configuration for a number of things already (though we wouldn't if the fontconfig default were sane for those use cases). What's the harm here? In which cases would you want to disable the font scanning?
I've added a debug program for that issue. commit d3e38c43834058cb95a6e5dcd5882816b3ab293c (HEAD -> master) Author: Bastien Nocera <hadess@hadess.net> Date: Tue Nov 3 16:38:52 2015 +0100 xsettings: Build the fontconfig monitor debug tool https://bugzilla.gnome.org/show_bug.cgi?id=585455
I think we can close this bug.
OK, thanks.