Age | Commit message (Collapse) | Author | Files | Lines |
|
It removes the code related to the old dialog icon
which is not displayed anymore.
The Gtk-CRITICAL error was caused by gtk_message_dialog_get_image returning NULL
as it is now deprecated in GTK 3.
taken from:
https://github.com/linuxmint/cinnamon-session/pull/71
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
compile fix for upower 0.99 series
|
|
upower 0.99 has lost support for hibernate and suspend. This leads to undefined
references to up_client_get_can_suspend and up_client_get_can_hibernate on my
system. This patch removes any call to those functions for upower >= 0.99.
|
|
this introduces a bit of code duplication but makes m-s-m independent
of any MATE packages which rely upon GTK+, and so makes it possible
to migrate m-s-m to GTK+3 right away.
of course, this change might be reverted in the future (when all of MATE
becomes GTK+3 only).
|
|
Ported from https://github.com/linuxmint/cinnamon-session/commit/73048abbfe05f882fed31365a1fe5b5733b6b7f6
|
|
This is necessary for compatibility and it brings support for many apps hardcoding GNOME support but also apps written in GTK (Gtk.Application taps into org.gnome.Session to register applications for a clean shutdown and for inhibition). It doesn't conflict with GNOME or Cinnamon (which both use the same name) since it's on the SessionBus. It makes mate-session aware of programs such as gedit, etc.. which might need to save people's work before logout, it brings support for totem inhibiting the session etc etc..
|
|
|
|
from https://github.com/GNOME/gnome-session/commit/f415130f0de6cdc13d9433632d5ee1554a242103
and https://github.com/GNOME/gnome-session/commit/378f502047022b263d14bbbec213ad442e5ad822
|
|
|
|
fixes https://github.com/mate-desktop/mate-session-manager/issues/76
taken from linuxmint/cinnamon-session@55538a5
|
|
fixes the issue with GLib >= 2.43,
https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619
|
|
|
|
fixes the issue with GLib >= 2.43,
https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619
Closes https://github.com/mate-desktop/mate-session-manager/pull/72
|
|
|
|
For example users may want to use a different ssh agent.
Debian bug:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775189msmgnome: Allow users to disable one or both compatibility options
|
|
This reverts commit f61b93311585587b105748b77b4b7279b5699a3e.
|
|
This reverts commit e017ed5b24f91705facec821afdc066f7a3523b5.
|
|
|
|
|
|
|
|
Closes https://github.com/mate-desktop/mate-session-manager/pull/67
|
|
This was making gnome-screensaver fade and blank the screen as soon as you
stopped moving the mouse/using the keyboard when the timeout is set to 0.
Based on gnome-session commit: be627c10409129408e135925d5dd83ae2d554fa0
From: Rodrigo Moya <[email protected]>
Original bug: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/863038
|
|
Disconnected is emitted when dbus is quitting. And all the dbus filters
might be interested in this signal, so never mark it as handled when we
look at it.
Based on gnome-commit: 67dd879fbe62bc28d3bbc48b88c3842e2cb827e8
From: Vincent Untz <[email protected]>
|
|
Scott already did some work on this, update to how gnome-session handles this.
Based on gnome-session commit: b2ad0abf2263b4af044388035df8993db9223a1b
From: Owen W. Taylor <[email protected]>
|
|
This gives clients who missed the SessionRunning signal a chance
to find out if the session has entered the running phase, and
lets us avoid race conditions.
Based on gnome-session commit: b59d358796343f81b31d4a398998faedd20b8f4b
From: Matthias Clasen <[email protected]>
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=636229
|
|
Based on gnome-session commit: ebf9afaa10c7903694df5b2fee635a6dde5213a6
From: Vincent Untz <[email protected]>
|
|
Based on gnome-session commit: 9f25b7599ba016f8da7275afa4c3f8e194678734
From: Vincent Untz <[email protected]>
|
|
Since setting some properties can be skipped, there is no guarantee that
SmProgram is set.
Based on gnome-session commit: 35a9945ae1339297de2e0eeff543e876186dea6e
From: Vincent Untz <[email protected]>
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=590828
|
|
In _xsync_alarm_set(), the positive and negative transition intervals
are set to the same value. However, the SYNC extension defines the
positive transition as set when the counter goes from strictly below the
threshold to greater than or equal to the threshold and similarly a
negative transition is triggered when the counter goes form strictly
greater than the threshold to less than or equal to the threshold.
Thus in the current set up there's a chance that the positive transition
can trigger, marking the session as idle, and some user input occur on
the same click so the IDLETIME count will hit the threshold but not go
above so the negative transition will not trigger. Thus the session will
not be marked as active.
The negative transition threshold should be set to 1ms less than the
positive transition to ensure that it always fires.
Based on gnome-session commit: 861313503a741f0129611ca005cf6d7c27124b54
From: Christopher Halse Rogers <[email protected]>
Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=627903
|
|
Based on gnome-session commit:fa30b73948c50c2493e19565b4e3b14b40f985e1
From: Vincent Untz <[email protected]>
|
|
Based on gnome-session commit: 899fe6b1628cd2d86931632f72512bca04d2aeaf
From: Vincent Untz <[email protected]>
|
|
|
|
On top of that, be a bit paranoid and ensure we don't log out in
end_phase() by checking the lockdown setting there too.
Based on gnome-session-commit: 107cfa7a4f6f43698407772e31472d742bdb219f
From: Vincent Untz <[email protected]>
|
|
Taken from gnome-session commit: 1e3e0b475cfd352d4abe7ace4ee5a40be04a8b42
From: Ray Strode <[email protected]>
|
|
When we get a logout request, there are two bits of information
that come with the request:
1) Whether or not we should seek confirmation by default from the user
before proceeding
2) Whether or not individual applications should be given an
opportunity to ask us to seek confirmation from the user before
proceeding.
We track the latter in a boolean state variable (forceful_logout),
but not the former.
We already have an enumeration type (GsmManagerLogoutMode) that can
be used to track both bits, though.
This commit changes the boolean state variable to the enum type, so
the whether-we-should-confirmation information is available deeper
down in the logout process.
Based on gnome-session commit: d7adaa9111d0f42d11225c7e29a7ee1d37d74d2f
From: Ray Strode <[email protected]>
|
|
If logout is forced, we don't want to show the inhibitor dialog.
A forced logout is one that shouldn't be "cancelable".
This commit prevents inhibitors from getting added if logout is
forced.
Based on gnome-session commit: bf1b6e8843b5e72d4f5a62a34eb322b82e33c2df
From: Ray Strode <[email protected]>
|
|
When the session manager enters the query end session phase,
it temporarily adds all clients to the "query clients" list.
This list is used to track the progression of clients quitting.
If a client quits during the query end session phase instead
of waiting until the end session phase, then it will get
destroyed but not get removed from the query clients list.
This commit removes it from the query clients list in this
case. It does this by explicitly invoking the end session
response handler (in effect, the client responded to the
end session query by exiting).
based on gnome-session commit: 8e6afcf1789c02692cf3b1ff3ee0a792d57e17a3
From: Ray Strode <[email protected]>
|
|
|
|
Based on gnome-session commit: 880379a8dd7181351ba49c579a5278d19eadc6b3
From Ryan Lortie <[email protected]>
|
|
XDG_CURRENT_DESKTOP is used by glib >= 2.42 at g_desktop_app_info* functions
Original GNOME commit: https://git.gnome.org/browse/gnome-session/commit/?id=1db085ce7e5197b28ab24a3ec54d888efe98fcb4
Closes https://github.com/mate-desktop/mate-session-manager/pull/62
|
|
|
|
|
|
0 disables timeout
|