| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
Right now if two session files have the same translated name, the login
screen will show both of them. There's no way the user can know which
session does which, so that's not a great user experience. Furthermore,
in the face of symlinks, both sessions truely could be identical.
This commit filters out the duplicates, so only one shows in the list.
Closes https://gitlab.gnome.org/GNOME/gdm/issues/437
|
| | |
|
| |\
| |
| |
| |
| | |
Get rid of most `g_type_class_add_private` occurrences (and use G_DECLARE_..._TYPE)
See merge request GNOME/gdm!55
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Note that we also removed the finalize() method, as that had become
empty and only gave warnings due to unused variables.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Note that we need to remove the signal vfunc in GdmSettingsClass, so
make sure to change the `g_signal_new("value-changed", ...)`, to cope
with that.
It also immediately gets rid of the deprecated
`g_type_class_add_private()`.
|
| |/
|
|
| |
This also gets rid of the deprecated `g_type_class_add_private()`
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Launch systemd service with KeyringMode=shared
See merge request GNOME/gdm!53
|
| |/
|
|
|
|
|
| |
This allows gdm to pass the LUKS password through to PAM.
The login keyring will now be unlocked automatically if autologin is
enabled!
|
| |
|
| |
This reverts commit 762b312bb98d31bd036fbcc8d61e53d5b1298d65
|
| |
|
|
|
| |
This allows gdm to pass the LUKS password through to PAM.
The login keyring will now be unlocked automatically if autologin is enabled!
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
manager: do initial-setup post work in manager code
See merge request GNOME/gdm!50
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
Right now we do the initial-setup related post work
when stopping the greeter, but the problem is we delay
stopping the greeter now until after the user session
is started.
That post-work needs to be done before the user session
is started.
This commit moves the code to a more logical place.
|
| |\
| |
| |
| |
| |
| |
| | |
manager: correct display confusion
Closes #426
See merge request GNOME/gdm!49
|
| |/
|
|
|
|
|
|
|
| |
commit c5c5bf1f reworked autologin and broke it.
This commit addresses the breakage by accessing
the proper display variable.
Closes https://gitlab.gnome.org/GNOME/gdm/issues/426
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Wip/gdm vt switch fixes
See merge request GNOME/gdm!48
|
| | |
| |
| |
| |
| |
| |
| |
| | |
We may end up re-using a display in waiting-to-finish state before it gets
finished in this case reset its state to managed to avoid it getting
finished while it is being used.
Closes https://gitlab.gnome.org/GNOME/gdm/merge_requests/45
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
We avoid changing to the login screen vt if we're already on it,
but the call is racy since we react to vt changes concurrently
with logind (who we query for the active vt).
This check drops the active vt check since it's pointless and
getting in the way.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The initial VT is in use check in on_vt_changed() is racy, when switching
to VT1 from an active session, on_vt_changed() may run before logind has
processed the VT change and then sd_seat_get_active() will return the
active session which we are switching away from. This results in the greeter
not being started on VT1.
On my system gdm reliably wins the race resulting in not getting a greeter
when manually switching from an active session to VT1.
gdm already starts the greeter unconditionally from
gdm_local_display_factory_sync_seats() on both startup and when an user
session exits. gdm also starts it unconditionally when selecting
"Switch user" from an user session.
Now autologin sessions avoid the initial VT as well.
So we now can assume that the initial VT is free for the login screen's
use. And create_display already checks for and re-uses
an existing greeter, so we can safely remove the racy check.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
tty1 is really meant for the login screen.
If a user autologins on it and we need a login
screen later, then the login screen has to go
in some auxiliary VT which isn't very nice.
This commit changes autologin to not use the
initial vt.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
At the moment we decide whether or not to perform autologin, by
looking at if the display is the initial VT display and if autologin
hasn't been started before.
That isn't going to work in the future when autologin is started
on a non-initial vt.
This commit changes GDM to instead check if the seat is seat0, and
if autologin hasn't run before, before deciding to do autologin.
|
| |/
|
|
|
|
|
|
| |
We automatically kill the login screen when switching VTs away
from it, but we should never kill the initial-setup screen in
that situation.
This commit adds a check to prevent that from happening.
|
| |\
| |
| |
| |
| | |
daemon: Move the waiting for the session to have taken over the fb to gdm-local-display-factory
See merge request GNOME/gdm!47
|
