| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Xlib will kill the process if it notices the display connection has
gone away. This is suboptimal for the main gdm process!
This commit ports the Xlib code to xcb, so it won't have the above
fragility.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The intention of the code is to only allow wayland login for
user sessions if the greeter session is also wayland.
Right now, that intention is only honored the first time a user
logs in.
This commit corrects the problem, to make sure sure we always avoid
wayland if the greeter session avoided wayland.
https://bugzilla.gnome.org/show_bug.cgi?id=775659
|
| |
|
|
|
|
|
|
|
| |
When a display registered, the sessions 'display-name' was already updated.
The displays 'x11-display-name' however was not, so I've just added that.
Of course that also meant that the 'x11-display-name' could no longer be
constructor only.
https://bugzilla.gnome.org/show_bug.cgi?id=752341
|
| | |
|
| | |
|
| |
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=772319
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 448134d3cdbc54e5359ea33d387993b0defdaefa changed gdm to
import the session from systemd --user.
Unfortunately, it broke log in after log out. The problem is, certain
session specific environment variables from the previous session
were getting leaked into the new session.
This commit wipes the ones causing the most problems on the GDM side,
but gnome-session should also probably purge them from the systemd
--user environment when it exits.
https://bugzilla.gnome.org/show_bug.cgi?id=771786
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
These files haven't been used since multistack became
a hard requirement.
|
| |
|
|
|
|
|
|
|
|
|
| |
In theory sending the password to them could be beneficial.
If for instance, they have pam_krb5 or pam_ecryptfs or pam_sss.
In practice, the stacks will fail if the passwords don't match,
and prevent autologin from continuing.
This commit just sidesteps them for now. Eventually,
authconfig/et al, will need to get updated to accomodate us.
|
| |
|
|
| |
It prevents postlogin from getting run.
|
| |
|
|
|
|
|
|
| |
commit bb12416da1f6 tries to make pam_gdm return AUTHINFO_UNAVAIL
if keyutils isn't around, but it inadvertently makes pam_gdm
return AUTHINFO_UNAVAIL when the password is available!
This commit fixes that.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The user may have configured the user environment via
user.conf or other means. This commit makes sure this session gets
those environment changes.
https://bugzilla.gnome.org/show_bug.cgi?id=736660
|
| |
|
|
|
|
|
| |
This makes it behave more like gdm-x-session. Also, we're
going to need the connection in a minute.
https://bugzilla.gnome.org/show_bug.cgi?id=736660
|
| |
|
|
|
|
|
|
|
|
|
| |
If pam_gdm fails we shouldn't call into pam_unix since it can lead
to the system asking for a password, and autologin isn't equipped for
that.
This commit changes the pam configuration to jump to pam_permit if
pam_gdm fails.
https://bugzilla.gnome.org/show_bug.cgi?id=770612
|
| |
|
|
|
|
|
|
| |
right now we return PAM_SUCCESS if keyutils are unavailable.
This is the wrong default, we should fail if we aren't able to
get the password.
https://bugzilla.gnome.org/show_bug.cgi?id=770612
|
| |
|
|
| |
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
DBUS_SESSION_BUS_ADDRESS is not the preferred way to find the session
bus these days. Instead it's expected to be found at $XDG_RUNTIME_DIR/bus
This commit changes the session launcher code, to just try to get a
connection to the bus explicitly, instead relying on
the presence of DBUS_SESSION_BUS_ADDRESS to know whether to start a
fallback bus.
https://bugzilla.gnome.org/show_bug.cgi?id=770395
|
| |
|
|
|
|
|
| |
I just noticed when reading the code that we pass a cancellable into
the function, but then don't use it.
https://bugzilla.gnome.org/show_bug.cgi?id=770396
|
| |
|
|
|
|
| |
Since it was dropped in gnome-settings-daemon 3.20
https://bugzilla.gnome.org/show_bug.cgi?id=770418
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If the user has an encrypted disk then systemd will cache the password
they type into the keyring. It makes sense to try to use this password
for automatic login purposes first, since on single user machines,
the sole user password is likely to match the disk password.
Of course if it doesn't work we'll fall back to the old way of doing
automatic login without a password (and then the user will have to
manualy enter if they need to for gnome-keyring or whatever)
https://bugzilla.gnome.org/show_bug.cgi?id=769950
|
| |
|
|
|
|
|
| |
It doesn't do anything yet, but it will eventually get used for
autologin purposes, and maybe other things.
https://bugzilla.gnome.org/show_bug.cgi?id=769950
|
| | |
|
| | |
|
| |
|
|
| |
It only has the chooser in it, so just move the chooser to the toplevel.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Future versions of gettext will fail if this header is missing.
|
| | |
|
| | |
|
| |
|
|
| |
(cherry picked from commit 2778a8a85f73dced81acca6ca2d7268572817d78)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
There's the potential for a crash in the shutdown path after the
factory is disposed, since we fail to disconnect signal handlers to
the displays / display store at factory dispose time.
This commit changes the g_signal_connect to g_signal_connect_object, to
avoid any potential for crash.
(this is a fix noticed when reading through the source. It's tangentially
related to a discussion on irc for a different bug)
|
| | |
|
| | |
|
| |
|
|
| |
(cherry picked from commit b5df2d64487923196c288843d9e8ff2e89b90e8b)
|
| | |
|
| | |
|
| | |
|
| | |
|
