| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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: 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]>
|
|
|
|
This reverts commit 80be90bb422ef8cb5a28c7ff3fe2a337dce8c368.
|
|
|
|
This commit is just an improved version of the pull request by Wolfgang Ulbrich
at https://github.com/mate-desktop/mate-session-manager/pull/38
making it working with both upower and systemd, and improving configure part
|
|
|
|
|
|
|
|
|
|
|
|
|
|
http://bazaar.launchpad.net/~lightdm-team/lightdm/trunk/view/head:/utils/gdmflexiserver
Closes #22 (https://github.com/mate-desktop/mate-session-manager/issues/22)
|
|
|
|
|
|
close https://github.com/mate-desktop/mate-desktop/issues/38
|
|
|
|
|
|
|
|
|
|
|
|
|
