| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
it's possible for different disks to have different encryption passwords
at startup.
In that case, we won't know which one to use, so bail.
https://bugzilla.gnome.org/show_bug.cgi?id=792339
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=787287
|
|
|
|
|
|
|
|
|
|
|
|
| |
DISPLAY and XAUTHORITY might not be set if we're starting the
X server as part of the session.
In that case we should ensure the variables aren't set in the
environment of the gdm session scripts.
This commit fixes that.
https://bugzilla.gnome.org/show_bug.cgi?id=792150
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=783082
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 89957be7b403811e85bc718908e12ece3c5f4113)
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=789722
|
|
|
|
|
|
|
| |
It's only needed to update the session type, which we do
earlier in the function anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=789722
|
|
|
|
|
|
| |
Most importantly, wait for the user settings to be loaded.
https://bugzilla.gnome.org/show_bug.cgi?id=789722
|
|
|
|
|
|
|
|
|
|
| |
We don't want to skip running initial setup if wayland
fell back or something.
This commit makes sure we only stop trying to start initial-setup
after it's completed.
https://bugzilla.gnome.org/show_bug.cgi?id=789434
|
|
|
|
|
|
| |
This provides gnome-shell with a way to use the new interface.
https://bugzilla.gnome.org/show_bug.cgi?id=788851
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds one PAM extension, a "Choice List" using the
new PAM_BINARY_PROMPT protocol added in the previous commit. The
PAM module sends a list of (key, row text) pairs, and GDM ferries
the request to gnome-shell using a new user verifier sub-interface.
gnome-shell should present the list to the user and pass back the
corresponding key, which GDM ferries back to the PAM module.
Note this commit is only the daemon side. A subsequent commit will
add the libgdm API needed for gnome-shell to actually deal with
this new PAM extension.
https://bugzilla.gnome.org/show_bug.cgi?id=788851
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This abuses PAM_BINARY_PROMPT for our own nefarious purposes.
The way it works is GDM advertises what "extensions" it supports
with the environment variable, GDM_SUPPORTED_PAM_EXTENSIONS (a space
separated list of reverse dns notation names). PAM services that
support this protocol, will read the environment variable, and
check for extension strings they support. They then know that sending
PAM_BINARY_PROMPT won't blow up, and know what format to use for the
binary data. The type field of the structure is the index of the
string from the environment variable.
This commit is just foundation work. It doesn't actually add any
extensions.
https://bugzilla.gnome.org/show_bug.cgi?id=788851
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
Right now we always give text responses back to pam modules,
so the response variable is named response_text. That's going
to change in the future, when we introduce private protocol for
the module to talk to GDM.
As prep work for that change, rename "response_text" to "response".
https://bugzilla.gnome.org/show_bug.cgi?id=788851
|
|
|
|
|
|
|
|
|
|
| |
This is done under the assumption that they are meant for Wayland only.
It is expected that a session called "foo" would have a "foo.desktop" file
under wayland-sessions/, a fallback "foo.desktop" under xsessions/, and
another "foo-xorg.desktop" under xsessions (that may simply be a symlink
to "foo.desktop") specifically for Wayland.
https://bugzilla.gnome.org/show_bug.cgi?id=788552
|
|
|
|
|
|
|
|
|
|
| |
commit 7e8243eecd0233f7ab92519207f2520794439b11 introduced a
compiler warning if gdm is built with --enable-wayland and
--disable-user-display-server
This commit fixes that.
https://bugzilla.gnome.org/show_bug.cgi?id=788963
|
|
|
|
|
|
|
| |
This used to be done with a special greeter indicator, but it's
much simpler to just define the presets accordingly.
https://bugzilla.gnome.org/show_bug.cgi?id=788942
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the user logs out we may detect the session dying before
we detect the X server dying. If that happens, then we
currently don't wait for the X server to exit before starting
a new X server.
This commit makes sure to explicitly kill the X server and wait
for its death before proceeding.
https://bugzilla.gnome.org/show_bug.cgi?id=788786
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Right now we end up writing wtmp entries for the login screen
user into /var/log/wtmp, but with a funky username of "(unknown)".
The login screen session shouldn't get a wtmp entry, and we
shouldn't ever add wtmp entries for sessions we don't know the username
for.
This commit fixes that.
https://bugzilla.gnome.org/show_bug.cgi?id=788784
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Use EXIT_ defines for readibility.
There were some exit codes > 1, but they don't seem to be checked by any of the
parent process code. This does mean that the logs might have changed, but
modern logging techniques have probably made this obsolete.
https://bugzilla.gnome.org/show_bug.cgi?id=788307
|