- 10 Oct, 2016 1 commit
-
-
Bastien Nocera authored
gnome-settings-daemon has been split up into separate daemons, which means we'll need to invoke those separately. See https://bugzilla.gnome.org/show_bug.cgi?id=772370 https://bugzilla.gnome.org/show_bug.cgi?id=772408
-
- 03 Sep, 2013 2 commits
-
-
Alban Crequy authored
gnome-initial-setup-copy-worker and gnome-keyring (and others) used to be started automatically by the session manager during the GSM_MANAGER_PHASE_INITIALIZATION phase. This is racy because gnome-keyring could read its file ~/.local/share/keyrings/login.keyring before it is written by gnome-initial-setup-copy-worker. The correct solution is to wait gnome-initial-setup-copy-worker finishes before starting other components in the initialization phase. I want to enforce this order without adding knowledge of gnome-initial-setup in gnome-keyring and others. It must also work on systems which don't use gnome-initial-setup. So I don't use a flag file in gnome-keyring's AutostartCondition to delay its startup. Instead, I add a new phase GSM_MANAGER_PHASE_EARLY_INITIALIZATION before the initialization phase. If no autostart desktop files use that phase, gnome-session will just go on to the next phase. But if gnome-initial-setup-copy-worker uses this new phase, it will ensure gnome-initial-setup-copy-worker finishes before the newly installed files in $HOME are read by anyone. Relevent documentation: https://wiki.gnome.org/SessionManagement http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html http://lists.freedesktop.org/archives/xdg/2007-January/007436.html https://bugzilla.gnome.org/show_bug.cgi?id=706692
-
Alban Crequy authored
-
- 06 Jan, 2009 1 commit
-
-
Lucas Rocha authored
2009-01-06 Lucas Rocha <lucasr@gnome.org> Bug 563640 – In all phases before APPLICATION, consider process termination as completion Most clients register using the session protocol. But it's perfectly fine if a client simply exits upon completion, or forks and exits in the parent when ready. This is indeed how we were treating phase INITIALIZATION. There is no reason to not treat other non-APPLICATION phases that way. The default clients for those phases (gnome-panel, metacity, nautilus) register to the session, but for example, libcanberra installed a script for phase DESKTOP to play login sound, and since it doesn't connect to the session, gnome-session was timeout'ing for that phase. * gnome-session/gsm-manager.c (on_app_exited, _start_app): ditto. Patch by Behdad Esfahbod. svn path=/trunk/; revision=5174
-
- 24 Mar, 2008 1 commit
-
-
Lucas Almeida Rocha authored
svn path=/trunk/; revision=4623
-