After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 559550 - [fontconfig] Does too much work during startup
[fontconfig] Does too much work during startup
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: plugins
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2008-11-06 03:39 UTC by Behdad Esfahbod
Modified: 2008-11-06 03:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
The patch (2.62 KB, patch)
2008-11-06 03:44 UTC, Behdad Esfahbod
committed Details | Review

Description Behdad Esfahbod 2008-11-06 03:39:24 UTC
My own bad.  Logging here for the record.  Currently we do a cache check when starting up.  That's stupid as fontconfig implicitly initalizes itself, then immediately stat everyone again to see if cache is up to date.  What we want instead is to explicitly initialize fontconfig to do any recaching as needed.

Patch coming.
Comment 1 Behdad Esfahbod 2008-11-06 03:43:15 UTC
Fixed.

2008-11-05  Behdad Esfahbod  <behdad@gnome.org>

        * plugins/xsettings/fontconfig-monitor.c (fontconfig_cache_init):
        * plugins/xsettings/fontconfig-monitor.h:
        * plugins/xsettings/gsd-xsettings-manager.c
        (start_fontconfig_monitor):  Only initialize fontconfig when starting
        up.  A cache update is redundant there. (bug #559550)

Comment 2 Behdad Esfahbod 2008-11-06 03:44:48 UTC
Created attachment 122074 [details] [review]
The patch