| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
At the moment the user's session is stored in a property called
"XSession". This is pretty weird if the user is using wayland.
AccountService now supports a more generic property "Session" and
a related "SessionType" property to replace "XSession".
This commit switches GDM over to use the new properties.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Right now the worker interface has three methods for starting
a conversation: Setup, SetupForUser, SetupForProgram
Each of these method calls take a large number of overlapping arguments.
Extending these argument lists is painful and breaks upgrades.
This commit adds a new, fourth call, Initialize, which supercedes the
others and just takes a vardict, which is much more extensible.
https://bugzilla.gnome.org/show_bug.cgi?id=788851
|
|
|
|
|
|
|
|
| |
It was used by ConsoleKit to set the "LoginWindow" property on
login screen sessions. it's not used by logind and ConsoleKit
is gone now, so drop it.
https://bugzilla.gnome.org/show_bug.cgi?id=743940
|
|
|
|
|
|
|
|
| |
The worker needs to know if a display should be forced on
vt1 or not when deciding which vt to allocate for the logind
session.
https://bugzilla.gnome.org/show_bug.cgi?id=744764
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=726380
|
|
|
|
|
|
|
|
|
|
|
| |
front"
This reverts commit 67235fd797e5b9a88178f4733551814b61a4711b.
As pointed out by Giovanni, this code is incorrect, as PAM_AUTHTOK
doesn't work when not in a PAM module.
https://bugzilla.gnome.org/show_bug.cgi?id=678057
|
|
|
|
|
|
|
| |
GdmSession expects to receive the service name along with the signal,
but the DBus interface does not include it, and this causes a crash.
https://bugzilla.gnome.org/show_bug.cgi?id=678057
|
|
|
|
|
|
|
|
| |
Some PAM modules can be told their password ahead of time to prevent them
having to ask later. This is accomplished by setting the PAM_AUTHTOK item
before calling pam_authenticate.
https://bugzilla.gnome.org/show_bug.cgi?id=678057
|
|
Before, the session worker and session communicated by a series of signals
and methods... but backwards. The session worker would listen for a series
of signals sent out by the session, and respond back by calling methods on
it. This requires a lot of annoying, silly manual labor when trying to add
another method to the API.
So, reverse the API so that the worker manager calls async methods on the
worker itself.
https://bugzilla.gnome.org/show_bug.cgi?id=678057
|