| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
a collection of the recent bits from master for 40.1
See merge request GNOME/gdm!149
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| | |
We don't need or want the login greeter to access accountsservice
for its session name
|
| |/
|
|
|
|
| |
Right now the session list comes out in hash table order.
This commit changes the code to sort by description.
|
| |\
| |
| |
| |
| | |
display: Handle failure before display registration
See merge request GNOME/gdm!145
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
Normally, e.g., gdm-wayland-session would register its display
before starting the session. This display registration is how
the display moves to the "managed" state. We currently detect
session failure in gdm_display_unmanage. If gdm-wayland-session
is killed before it registers the display, gdm_display_unmanage
won't run, and failure won't be detected.
This commit make gdm_display_unmanage get called, even if the
display isn't yet fully managed.
|
| |\
| |
| |
| |
| | |
gdm-runtime-config: end lines in output
See merge request GNOME/gdm!139
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Read XDG_DATA_DIRS from env.d for initial-setup
See merge request GNOME/gdm!140
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the initial setup session we may need to run a Flatpak application;
Flatpak requires XDG_DATA_DIRS to include its locations to work
correctly, but that's not set at the moment for the initial-setup
session.
This commit borrows the code from GdmSessionWorker to read
XDG_DATA_DIRS from gdm's env.d machinery for the initial-setup session
as well.
|
| |/
|
|
|
| |
We need to use this machinery from a second location; as a first step
factor it out to gdm-common.
|
| |\
| |
| |
| |
| | |
meson: Fix libwrap detection
See merge request GNOME/gdm!142
|
| |/
|
|
| |
Bug: https://bugs.gentoo.org/790671
|
| |\
| |
| |
| |
| | |
session: Only emit verification-complete on reauth or after session is opened
See merge request GNOME/gdm!143
|
| | |
| |
| |
| |
| |
| |
| |
| | |
We used the same signal (session-start-failed) when we had both session
starting and opening failures.
This may lead to wrong behaviors, so let's introduce another signal to
notify such state.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're currently emitting verification-complete signal as soon as we
got a positive authentication callback from the worker, however at this
point we've not opened the session yet, and if that fails we'll end up
in a scenario where gdm assumed that we're logging in, and so its
greeter is shut down and never restarted on its VT until we manually
switch back and forth from it. Meanwhile the session opening failure is
never exposed to the user.
So, do not emit verification-completed on logins, until we've opened
the session.
However, re-order the session-opened callback events so that we keep
notifying verification-complete before than session-opened.
This basically reverts commit c4292870 (again).
Fixes: https://gitlab.gnome.org/GNOME/gdm/-/issues/712
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
meson: Fix localedir summary
See merge request GNOME/gdm!138
|
| |/
|
|
|
|
|
| |
In the commit mentioned below, the actual setting was fixed but the
summary was forgotten.
Fixes: 5d5bc0f4 ("meson: Fix location of locale directory")
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Use the last cryptsetup password with PAM
Closes #657
See merge request GNOME/gdm!136
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
pam-arch: Update to match pambase 20200721.1-2
See merge request GNOME/gdm!135
|
| |/
|
|
|
|
|
| |
Update the PAM files for Arch Linux. This has been applied downstream
since Aug 2020.
https://bugs.archlinux.org/task/67485
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The idle callback was defined as a void function rather than returning a
boolean as it should. This meant that the return value may end up being
non-zero in some situations causing an infinite loop.
This seems to only happen on aarch64 and possibly only with certain
compiler versions.
Closes: #668
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
session: Initialize DBus error domain before resolving errors
See merge request GNOME/gdm!132
|
| |/
|
|
|
|
|
|
|
|
|
| |
We would not initialize the DBus error domain before we retrieved the
first error, but only did so to compare the error after receiving them.
This means that the first error we received will not be resolved
correctly, while all subsequent ones are resolved.
Fix this by calling GDM_SESSION_WORKER_ERROR from gdm_session_class_init
and add gdm_dbus_error_ensure to make sure this can never be optimized
away.
|
| |\
| |
| |
| |
| | |
local-display-factory: Fix wait for graphical
See merge request GNOME/gdm!133
|
| |/
|
|
|
|
|
|
| |
In commit a37e5a950fbd ("local-display-factory: Wait for seats to become
graphical") we introduced logic to wait for up to 10s for the seat to
become graphical before trying to use it. Unfortunately, the logic was
slightly wrong, resulting us to immediately do the fallback rather than
waiting.
|
| | |
|
