commit 2917d5effef9b87ba815a973fb81111b6e01f654 (HEAD, tag: 3.9.91, origin/master, origin/HEAD, master) Author: Ray Strode AuthorDate: Tue Sep 3 10:23:36 2013 -0400 Commit: Ray Strode CommitDate: Tue Sep 3 10:26:01 2013 -0400 configure: bump to 3.9.91 M configure.ac commit 9c469494941cc15c5d266ebeb3052178c91c7689 Author: Ray Strode AuthorDate: Tue Sep 3 10:25:49 2013 -0400 Commit: Ray Strode CommitDate: Tue Sep 3 10:26:01 2013 -0400 NEWS: update for release M NEWS commit e2fb2ef71c89fe85e510f4a823797f2808990fee Author: Giovanni Campagna AuthorDate: Wed Aug 21 10:25:27 2013 +0200 Commit: Ray Strode CommitDate: Tue Sep 3 10:20:11 2013 -0400 GsmManager: don't attempt to restart a wayland compositor There is no point in restarting it, the session is already gone. And we can't show a fail whale either, so just log a message to the journal and die. https://bugzilla.gnome.org/show_bug.cgi?id=706420 M gnome-session/gsm-manager.c commit 705699b2799a3434d1a8f35c9a92868a5057f73e Author: Giovanni Campagna AuthorDate: Tue Aug 20 11:10:52 2013 +0200 Commit: Ray Strode CommitDate: Tue Sep 3 10:05:28 2013 -0400 Stop connecting to the X11 server Remove all GTK+ code from the main gnome-session binary (including the two fallback mode dialogs), so that gnome-session can run when X is not available. These dialogs are no longer used anymore, so it's not a UI freeze break. https://bugzilla.gnome.org/show_bug.cgi?id=706420 M configure.ac M data/Makefile.am D data/gsm-inhibit-dialog.ui M gnome-session/Makefile.am D gnome-session/gsm-inhibit-dialog.c D gnome-session/gsm-inhibit-dialog.h D gnome-session/gsm-logout-dialog.c D gnome-session/gsm-logout-dialog.h M gnome-session/gsm-manager.c M gnome-session/gsm-util.h M gnome-session/main.c M po/POTFILES.in commit 672cb149b846597e7d3cb66692d31a7df5450ee2 Author: Giovanni Campagna AuthorDate: Tue Aug 20 15:11:08 2013 +0200 Commit: Ray Strode CommitDate: Tue Sep 3 09:38:26 2013 -0400 Add a new autostart phase, DisplayServer, that runs before Initialization This way, the wayland compositor can initialize (and spawn XWayland) before gnome-settings-daemon starts. https://bugzilla.gnome.org/show_bug.cgi?id=706420 M gnome-session/gsm-autostart-app.c M gnome-session/gsm-manager.c M gnome-session/gsm-manager.h commit c12678b59ccc3f03ea4886345b6676a6b92ca304 Author: Giovanni Campagna AuthorDate: Tue Aug 20 11:24:07 2013 +0200 Commit: Ray Strode CommitDate: Tue Sep 3 09:33:50 2013 -0400 fail-whale: don't rely on the x11 GTK backend This way, we can run as a wayland client, in case XWayland crashed. https://bugzilla.gnome.org/show_bug.cgi?id=706420 M gnome-session/gsm-fail-whale-dialog.c commit d19cf2d981811e32640a89ce7af7c9202f95d1d5 Author: Giovanni Campagna AuthorDate: Tue Aug 20 11:09:01 2013 +0200 Commit: Ray Strode CommitDate: Tue Sep 3 09:32:50 2013 -0400 GsmManager: remove obsolete code for talking with GDM These days shutdown and reboot is handled by logind everywhere, no need for this ancient code. https://bugzilla.gnome.org/show_bug.cgi?id=706420 A data/gnome-wayland.session.desktop.in.in M gnome-session/Makefile.am D gnome-session/gdm.c D gnome-session/gdm.h M gnome-session/gsm-manager.c commit 3e8f8d083686d49fd866a582a5895ba834227685 Author: Alban Crequy AuthorDate: Mon Aug 19 21:13:45 2013 +0100 Commit: Ray Strode CommitDate: Tue Sep 3 09:31:32 2013 -0400 add new phase: GSM_MANAGER_PHASE_EARLY_INITIALIZATION 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 M gnome-session/README M gnome-session/gsm-autostart-app.c M gnome-session/gsm-manager.c M gnome-session/gsm-manager.h commit 3523fb28bda0396fd87c409d4c310d5680f0837f Author: Alban Crequy AuthorDate: Mon Aug 19 20:38:53 2013 +0100 Commit: Ray Strode CommitDate: Tue Sep 3 09:31:25 2013 -0400 gnome-session/README: rename enum to match the code M gnome-session/README commit 6c24fcc915019ebb93fa25866ba17cd668656338 Author: Cosimo Cecchi AuthorDate: Mon Sep 2 02:16:34 2013 -0700 Commit: Ray Strode CommitDate: Tue Sep 3 08:49:48 2013 -0400 manager: fix deadlock when registering XSMP clients at login gnome-session will switch to the next phase whenever the list of applications pending registration is emptied. Previously, for XSMP clients, the code in GsmXSMPClient would signal that an application was registered before sending the reply through SmsRegisterClientReply(). As GnomeIdleMonitor will now call into Mutter through DBus, and the RUNNING phase of the session will initialize its presence component that uses the monitor, we will end up in a situation where Mutter is waiting for the XSMP reply from gnome-session, and gnome-session is waiting for a synchronous DBus reply from Mutter, effectively locking up the login process until the DBus timeout occurs. This commit fixes the bug by signalling XSMP app registration only after the reply has been sent over the wire. https://bugzilla.gnome.org/show_bug.cgi?id=707274 M gnome-session/gsm-manager.c M gnome-session/gsm-xsmp-client.c M gnome-session/gsm-xsmp-client.h commit 2040b88847ed1ee11182caac96b0f09c553c646e Author: Ray Strode AuthorDate: Tue Aug 27 17:24:48 2013 -0400 Commit: Ray Strode CommitDate: Wed Aug 28 09:07:44 2013 -0400 manager: make Shutdown/Reboot D-Bus APIs failable Right now Shutdown and Reboot return as soon as the operations are initiated. This means we get no notification if the operation is cancelled by the user later. This commit defers returning unless it's clear whether or not the operation will go through. https://bugzilla.gnome.org/show_bug.cgi?id=706676 M gnome-session/gsm-manager.c M gnome-session/gsm-manager.h M gnome-session/org.gnome.SessionManager.xml commit ac9fd0dc97a17674cb082f80df0b1fcc45bc92bf Author: Kalev Lember AuthorDate: Thu Aug 22 19:58:32 2013 +0200 Commit: Kalev Lember CommitDate: Thu Aug 22 20:21:29 2013 +0200 Rename the desktop file to gnome-session-properties.desktop ... so that it matches up with the executable gnome-session-properties name. https://bugzilla.gnome.org/show_bug.cgi?id=706611 M configure.ac M data/Makefile.am R100 data/session-properties.desktop.in.in data/gnome-session-properties.desktop.in.in M po/POTFILES.in M po/POTFILES.skip commit 7f0d2ad091e8591b4a810fe1d8d7dd3bfd740f5c Author: Maxime Villard AuthorDate: Wed Aug 21 09:27:52 2013 -0400 Commit: Ray Strode CommitDate: Wed Aug 21 09:27:52 2013 -0400 Drop dead code M gnome-session/gsm-autostart-app.c M gnome-session/gsm-inhibit-dialog.c M gnome-session/gsm-manager.c M gnome-session/gsm-session-save.c M tools/gnome-session-check-accelerated.c commit 6bb078e856b7cf95e2cbd3518e18d6b875c2ce2b Author: Maxime Villard AuthorDate: Wed Aug 21 09:27:09 2013 -0400 Commit: Ray Strode CommitDate: Wed Aug 21 09:27:09 2013 -0400 gnome-session: fix uninitialzed variable warnings M gnome-session/gsm-dbus-client.c M gnome-session/gsm-logout-dialog.c commit 6de7237806146e7042ba093cd190f17f7c019267 (tag: 3.9.90)