GNOME Bugzilla – Bug 328441
gnome-screensaver-dialog is slooooow
Last modified: 2006-01-25 17:34:01 UTC
Please describe the problem: So, from the time I hit a key to the time I see the unlock dialog is often multiple seconds - sometimes up to 10 seconds. I figured I'd see what it was doing. gnome-screensaver-dialog: - attempts to open 1638 files - succeeds in opening 685 files This very well may not be g-s-d's fault, but something needs fixed in the stack. Steps to reproduce: 1. start gnome-screensaver 2. lock screen 3. hit a key Actual results: ... churn ... strace attached. Expected results: dialog pops up like *snap* that! Does this happen every time? The amount of time varies, probably due to disk cache issues. Other information: $ rpm -q gnome-screensaver gtk2 pango fontconfig freetype gnome-screensaver-2.13.5-4 gtk2-2.8.10-4 pango-1.11.2-1 fontconfig-2.3.93-4 freetype-2.1.10-5.1
Created attachment 58022 [details] strace of gnome-screensaver-dialog Here's the strace. Warning: ~1 MB
Are you using a Fedora themed dialog? It uses glade. Also there is some profiling code that can be enabled at build time. Can you enable it and run the gnome-screensaver-dialog command in a terminal, and post the results here? Thanks.
Oh, and is this with user switching enabled or disabled?
Stock dialog (odd, why can't the 'blank screen only' option use a themed dialog :) ), and user switching disabled. I suspect the problem lies in fontconfig/freetype somewhere, from an examination of what it's trying to open.
Created attachment 58023 [details] strace #2 Here's the strace when built with PROFILE_LOCK_DIALOG.
OK, yeah now that I actually look at the trace... oh my god. I guess you have a lot more fonts than I do but still. Any ideas about what we can do? Is there a way to make the loading lazy or more on-demand?
Not sure. Perhaps need to check with the fontconfig maintainers?
OK, appears to have been a local fontconfig issue.