GNOME Bugzilla – Bug 95179
gnome-settings-daemon needlessly slowing down login by synching gconf database
Last modified: 2007-07-29 20:05:58 UTC
A number of gconf keys are set by the gnome-settings-daemon at login time, which causes the gconf database to get synched. This slows things down. This window_manager keys get set: /desktop/gnome/applications/window_manager/default Furthermore, the following a11y-related gconf keys are set during login. According to Jody Goldberg (on gnome-hackers list), "This is a side effect of monitoring the XKB state in the server, when we load the values from gconf it triggers an event from the X server which causes us to reload from the X server. It should not be hard to notice that the X server is not changing any gconf state and avoid doing the assignment." It would speed login if these keys were not written at every login (and the resulting gconf sync were avoided) except when the values have changed and require updating gconf. In the general case, the values are just updated with the same values that were there before. --list of keys currently being written-- /desktop/gnome/accessibility/keyboard/enable /desktop/gnome/accessibility/keyboard/feature_state_change_beep /desktop/gnome/accessibility/keyboard/timeout /desktop/gnome/accessibility/keyboard/bouncekeys_delay /desktop/gnome/accessibility/keyboard/bouncekeys_beep_reject /desktop/gnome/accessibility/keyboard/mousekeys_max_speed /desktop/gnome/accessibility/keyboard/mousekeys_accel_time /desktop/gnome/accessibility/keyboard/mousekeys_init_delay /desktop/gnome/accessibility/keyboard/slowkeys_beep_press /desktop/gnome/accessibility/keyboard/slowkeys_beep_accept /desktop/gnome/accessibility/keyboard/slowkeys_beep_reject /desktop/gnome/accessibility/keyboard/slowkeys_delay /desktop/gnome/accessibility/keyboard/stickykeys_two_key_off /desktop/gnome/accessibility/keyboard/stickykeys_modifier_beep /desktop/gnome/accessibility/keyboard/enable /desktop/gnome/accessibility/keyboard/feature_state_change_beep /desktop/gnome/accessibility/keyboard/timeout /desktop/gnome/accessibility/keyboard/bouncekeys_delay /desktop/gnome/accessibility/keyboard/bouncekeys_beep_reject /desktop/gnome/accessibility/keyboard/mousekeys_max_speed /desktop/gnome/accessibility/keyboard/mousekeys_accel_time /desktop/gnome/accessibility/keyboard/mousekeys_init_delay /desktop/gnome/accessibility/keyboard/slowkeys_beep_press /desktop/gnome/accessibility/keyboard/slowkeys_beep_accept /desktop/gnome/accessibility/keyboard/slowkeys_beep_reject /desktop/gnome/accessibility/keyboard/slowkeys_delay /desktop/gnome/accessibility/keyboard/stickykeys_two_key_off /desktop/gnome/accessibility/keyboard/stickykeys_modifier_beep
Actually there was an even earlier thinko that was causing this. We were installing the monitoring filter _before_ we assigned the gconf values to the x server. However, I had already coded up the more difficult test, so both fixes can go in. patch applied to both branches.
The patch gets rid of all the a11y keys, but this one is still being written to, so the gconf sync is still happening: /desktop/gnome/applications/window_manager/default Can this one be eliminated as well?
I'll have a look today.
Jody, can you take care of this last one?
Jody, did you ever take a look at this? Is it still relevant?
Still relevent Didn't look
ping : can someone approve this (very small) change ?
ping again.
Ping yet again.
Vincent, Jody, can you enlighten me on what the change is? I didn't see the original patch Jody 'applied to both branches', so I'm not really sure what the change was.
Rodrigo, these[1] are the changes that Jody commited, hope this is useful for you. [1] http://tinyurl.com/yac5x4 (thanks Bonsai)
I can't see where the current code would try to touch the window_manager setting. If this is still relevant could somebody please supply that bit of info?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!