Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Launch gnome-keyring-daemon asynchronously, and remove the
GNOME_KEYRING_PID reading code.
GNOME_KEYRING_PID exposure was removed from gnome-keyring in 2014.
|
|
Keyring lifetime fd was removed from gnome-keyring in 2009
See "[daemon] Use new control protocol for daemon."
|
|
|
|
|
|
|
|
|
|
|
|
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 <[email protected]>
Co-authored-by: Jorge Pizarro Callejas <[email protected]>
|
|
|
|
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
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=764029
Adapted from https://gitlab.gnome.org/GNOME/gnome-session/commit/f708bbbf
|
|
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
|
|
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
|
|
|
|
|
|
- mate-session/Makefile.am
- mate-session/test-client-dbus.c
|
|
|
|
- capplet/gsm-app-dialog.c
- capplet/gsm-app-dialog.h
- capplet/gsm-properties-dialog.c
- capplet/gsm-properties-dialog.h
- capplet/gsp-app-manager.c
- capplet/gsp-app-manager.h
- capplet/gsp-app.c
- capplet/gsp-app.h
- mate-session/gsm-app.c
- mate-session/gsm-app.h
- mate-session/gsm-autostart-app.c
- mate-session/gsm-autostart-app.h
- mate-session/gsm-client.c
- mate-session/gsm-client.h
- mate-session/gsm-consolekit.c
- mate-session/gsm-consolekit.h
- mate-session/gsm-dbus-client.c
- mate-session/gsm-dbus-client.h
- mate-session/gsm-inhibit-dialog.c
- mate-session/gsm-inhibit-dialog.h
- mate-session/gsm-inhibitor.c
- mate-session/gsm-inhibitor.h
- mate-session/gsm-logout-dialog.c
- mate-session/gsm-logout-dialog.h
- mate-session/gsm-store.c
- mate-session/gsm-store.h
- mate-session/gsm-systemd.c
- mate-session/gsm-systemd.h
- mate-session/gsm-xsmp-client.c
- mate-session/gsm-xsmp-client.h
- mate-session/gsm-xsmp-server.c
- mate-session/gsm-xsmp-server.h
|
|
Fixes the issue with GLib >= 2.58, list of modified files:
- mate-session/gsm-presence.c
- mate-session/gsm-presence.h
|
|
Fixes the issue with GLib >= 2.58, list of modified files:
- mate-session/gsm-manager.c
- mate-session/gsm-manager.h
|
|
Fixes the issue with GLib >= 2.58, list of modified files:
- mate-session/gs-idle-monitor.c
- mate-session/gs-idle-monitor.h
|
|
Fixes the issue with GLib >= 2.58, list of modified files:
- mate-session/mdm-signal-handler.c
- mate-session/mdm-signal-handler.h
|
|
Run with --version, only show the application name and version, not show
the path of program.
|
|
|
|
|
|
ignoring return value of ‘fscanf’, declared with attribute warn_unused_result
|
|
same as done in:
https://github.com/mate-desktop/mate-polkit/commit/ed37b52fbfbce5d57d0549fac1a9dca2502f3372
fixes https://github.com/mate-desktop/mate-session-manager/issues/123
fixes https://github.com/mate-desktop/mate-session-manager/issues/140
|
|
|
|
enviroment when the session starts.
If we get passed an environment variable, send it along to the
systemd --user session so things running in that context can pick
it up.
See: https://bugzilla.gnome.org/show_bug.cgi?id=736660
|
|
the session starts.
dbus-update-activation-environment excepts certain environment
variables, that systemd won't. We're going to want to eventually
send the environment to systemd, too, so we should make sure the
same set of variables get sent to both.
See: https://bugzilla.gnome.org/show_bug.cgi?id=736660
|
|
This requires ConsoleKit2 version 0.9.2.
+ corrections for issues mentioned at https://github.com/mate-desktop/mate-session-manager/pull/133
|
|
|
|
|
|
this should ensure that mate-session won't listen to TCP ports.
if needed, this check can be disabled using --without-xtrans option.
fixes https://github.com/mate-desktop/mate-session-manager/issues/131
adapted from:
https://git.gnome.org/browse/gnome-session/commit/?id=aa4c9d125012ae94154ce075d62342b63b41a7d9
|
|
In some systems the gdm binary is actually called "gdm-binary", so we
need to check for that too.
|