summaryrefslogtreecommitdiff
path: root/mate-session
AgeCommit message (Collapse)AuthorFilesLines
2017-02-27fix indent of some #if's to match the rest of the filemonsta1-8/+8
2017-01-18build: check stricter for presence of xtransmonsta1-4/+4
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
2016-10-19Also look for gdm-binary processGeorge Vlahavas1-1/+1
In some systems the gdm binary is actually called "gdm-binary", so we need to check for that too.
2016-08-03Fix Gtk-CRITICAL error caused by deprecated coderaveit651-5/+0
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
2016-05-17require GTK+ >= 3.14, drop GTK+2 code and --with-gtk build optionmonsta4-95/+0
2016-01-31Adding #include <signal.h> for FreeBSD supportEric Turgeon1-0/+2
2015-12-31mdm: fix logic errormonsta1-1/+1
2015-12-13fix a typo in a warningMonsta1-2/+2
2015-12-13fix logic error that caused a weird build warningMonsta1-1/+1
2015-12-13fix one more build warningMonsta1-1/+2
2015-12-13fix warnings about unused variablesMonsta1-18/+6
2015-12-13Merge pull request #110 from oleid/mastermonsta2-10/+10
compile fix for upower 0.99 series
2015-11-14compile fix for upower 0.99 seriesOlaf Leidinger2-10/+10
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.
2015-11-11get rid of dependency on libmate-desktopmonsta1-3/+17
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).
2015-10-15Only wait 1 second max on logout/shutdownClement Lefebvre1-1/+6
Ported from https://github.com/linuxmint/cinnamon-session/commit/73048abbfe05f882fed31365a1fe5b5733b6b7f6
2015-09-04Use org.gnome.SessionManager at /org/gnome/SessionManager as the DBUS API. ↵Clement Lefebvre17-60/+60
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..
2015-09-01Add option to disable overlay scrollinginfirit1-0/+23
2015-07-27clean up and de-duplicate definesMonsta8-16/+4
from https://github.com/GNOME/gnome-session/commit/f415130f0de6cdc13d9433632d5ee1554a242103 and https://github.com/GNOME/gnome-session/commit/378f502047022b263d14bbbec213ad442e5ad822
2015-06-28Fix uninitialized variable usages for !HAVE_UPOWEROBATA Akio1-2/+2
2015-04-01ckeck-for-running DM for user switchingraveit651-42/+43
fixes https://github.com/mate-desktop/mate-session-manager/issues/76 taken from linuxmint/cinnamon-session@55538a5
2015-02-25debug GSettings: first connect to settings, then read them.Monsta1-3/+4
fixes the issue with GLib >= 2.43, https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619
2015-02-25make indentation more consistent, removed excessive var assignmentMonsta1-8/+6
2015-02-25first connect to settings, then read them.Monsta1-1/+2
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
2015-01-20MsmGnome: Fix and simplify logicColomban Wendling1-23/+15
2015-01-13MsmGnome: Allow users to disable compatibility optionsinfirit1-5/+36
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
2014-12-16Revert "Revert "Drop support for Glib < 2.36""infirit1-4/+0
This reverts commit f61b93311585587b105748b77b4b7279b5699a3e.
2014-12-16Revert "Drop support for Glib < 2.36"infirit1-0/+4
This reverts commit e017ed5b24f91705facec821afdc066f7a3523b5.
2014-12-15avoid dereferencing NULL pointerMonsta1-3/+5
2014-12-15Update configure.acposophe1-0/+2
2014-11-18logout-dialog: Fix stupid mistake in ccfc0f67de5e6b15a1c7e33f45c671bc2cebd4b4infirit1-4/+5
2014-11-11Properly init boolean variable and don't leak memorymonsta2-2/+3
Closes https://github.com/mate-desktop/mate-session-manager/pull/67
2014-11-07gsm: Refuse to install an idle timeout of 0 secondsinfirit1-1/+2
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
2014-11-07gsm: Never mark as handled the Disconnected signal from dbusinfirit1-1/+2
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]>
2014-11-07Fix usage of %lld for 64-bit formatsinfirit1-5/+5
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]>
2014-11-07Add an IsSessionRunning methodinfirit3-1/+30
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
2014-11-07gsm: Add gtk-doc comments for two GsmClient functionsinfirit1-0/+17
Based on gnome-session commit: ebf9afaa10c7903694df5b2fee635a6dde5213a6 From: Vincent Untz <[email protected]>
2014-11-07gsm: Do not uselessly duplicate a stringinfirit1-6/+5
Based on gnome-session commit: 9f25b7599ba016f8da7275afa4c3f8e194678734 From: Vincent Untz <[email protected]>
2014-11-07gsm: Do not assume XSMP clients set the SmProgram propertyinfirit1-3/+20
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
2014-11-07gsm: Fix race condition in idle monitorinfirit1-0/+1
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
2014-11-07gsm: Support disable-user-switching lockdown setting in logout dialoginfirit1-5/+16
Based on gnome-session commit:fa30b73948c50c2493e19565b4e3b14b40f985e1 From: Vincent Untz <[email protected]>
2014-11-07gsm: Enforce disable-user-switching lockdown settinginfirit1-1/+24
Based on gnome-session commit: 899fe6b1628cd2d86931632f72512bca04d2aeaf From: Vincent Untz <[email protected]>
2014-11-07lockdown: Add define for disable-log-outinfirit1-1/+2
2014-11-04gsm: Also support disable-log-out for Shutdown/CanShutdown dbus methodsinfirit1-10/+30
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]>
2014-11-04Improve logout lockdowninfirit2-0/+17
Taken from gnome-session commit: 1e3e0b475cfd352d4abe7ace4ee5a40be04a8b42 From: Ray Strode <[email protected]>
2014-11-04manager: track full details of logout requestinfirit1-31/+42
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]>
2014-11-04manager: don't ever show inhibitor dialog if logout is forcedinfirit1-3/+21
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]>
2014-11-04manager: remove client from query clients list on disconnectinfirit1-6/+47
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]>
2014-11-04Use resizable property instead of allow-grow allow-shrinkinfirit1-2/+1
2014-11-04gsettings: stop using g_settings_list_schemas()infirit1-22/+20
Based on gnome-session commit: 880379a8dd7181351ba49c579a5278d19eadc6b3 From Ryan Lortie <[email protected]>
2014-09-29Set XDG_CURRENT_DESKTOP if unsetDenis Gorodnichev1-0/+3
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
generated by cgit v1.2.1 (git 2.18.0) at 2024-12-01 01:29:45 +0000