GNOME Bugzilla – Bug 686814
Fix the startup ordering
Last modified: 2012-10-26 09:40:36 UTC
Commit dcb54d8 makes us call RegisterClient before we could get to Setenv. I'm proposing that we revert it and then only start the settings manager object in on_client_registered(). I'm not sure of one thing though. Should we terminate the daemon by calling gtk_main_quit() in the error branch of on_client_registered() and only start the manager in the non-error branch? Or does it make sense to still start the manager in case the registration failed (this is what's implemeted here) ?
Created attachment 227175 [details] [review] Revert "main: Ensure session registration happens before other idles" This reverts commit dcb54d8a1c4ecacf6fbe17bdffefdca3b1e6d2d5.
Created attachment 227176 [details] [review] main: Only start the manager after registering with gnome session This ensures that any idles will only run after RegisterClient but also that we only call RegisterClient after Setenv as otherwise Setenv isn't effective.
Review of attachment 227176 [details] [review]: Fine by me.
Attachment 227175 [details] pushed as 1d4f68d - Revert "main: Ensure session registration happens before other idles" Attachment 227176 [details] pushed as c38e155 - main: Only start the manager after registering with gnome session