mate-session-manager/mate-session, branch 1.22

Fix timeout with gnome-keyring 3.34

2019-10-08T13:00:48+00:00

Launch gnome-keyring-daemon asynchronously, and remove the
GNOME_KEYRING_PID reading code.

GNOME_KEYRING_PID exposure was removed from gnome-keyring in 2014.

Remove GNOME_KEYRING_LIFETIME_FD

2019-10-08T13:00:35+00:00

Keyring lifetime fd was removed from gnome-keyring in 2009

See "[daemon] Use new control protocol for daemon."

Add ELOGIND support

2019-03-21T12:35:12+00:00

Reuses HAVE_SYSTEMD #define to reduce #ifdef mess.

ELOGIND is not officially supported, but since it's
a subset of systemd, it should work out of the box.

Co-authored-by: Joakim Tjernlund 
Co-authored-by: Jorge Pizarro Callejas

Guard against missing systemd

2019-03-07T14:45:59+00:00

manager: restart user bus if last graphical session

2019-02-04T12:52:05+00:00

There are desktop services (such as goa-daemon, e-d-s, etc)
that don't open the display, but rely on dbus-daemon to scope
the session. These days dbus-daemon is a user bus, not a sesssion,
bus which leaves these services alive after log out.

This commit checks to see if we're the last desktop session for the
user at log out time, and if so, restarts the dbus daemon. This
will lead to existing clients getting booted and die, but allow user
bus clients that want to outlive a session to stick around if they so
desire.

Longer term, clients should stop relying on the session bus to define
their lifetime.

https://bugzilla.gnome.org/show_bug.cgi?id=764029
Adapted from https://gitlab.gnome.org/GNOME/gnome-session/commit/97d1cf5

systemd: add api for detecting if this is the last session for a user

2019-02-04T12:52:05+00:00

https://bugzilla.gnome.org/show_bug.cgi?id=764029
Adapted from https://gitlab.gnome.org/GNOME/gnome-session/commit/f708bbbf

gsm: Disconnect all dbus clients when dbus is disconnected

2019-02-04T12:52:05+00:00

When we receive the Disconnected signal from dbus on the session bus,
then we know we won't be able to talk to dbus clients anymore, so mark
them as disconnected. Also, do not restart them even if they're supposed
to be autorestarted, as we won't be able to track them.

At this point, the session is kind of hosed. We could possibly decide
to simply leave, but we don't do it in case it's a user session and
there's unsaved data.

This helps a lot in the case of the gdm greeter, see
https://bugzilla.gnome.org/show_bug.cgi?id=658481
Adapted from https://gitlab.gnome.org/GNOME/gnome-session/commit/ae8fa537

manager: don't wait for all clients to exit before exiting

2019-02-04T12:52:05+00:00

If a client gets hung up, we shouldn't hold up going to login screen.
It means making a bug in a single client break the desktop.

https://bugzilla.gnome.org/show_bug.cgi?id=750508
Adapted from https://gitlab.gnome.org/GNOME/gnome-session/commit/58c9323e

[gsm-autostart-app] Migrate from dbus-glib to gdbus

2019-01-30T06:05:39+00:00

avoid 'gtk_dialog_add_button' with stock ids

2018-12-15T21:47:22+00:00