| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
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: Wait for seats to become graphical
Closes #662
See merge request GNOME/gdm!128
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It may happen that seats are not graphical initially because the DRM
device is not ready yet. In that case, ignore the seat and wait for the
CanGraphical property notification in order to add it at that point.
However, there are some rare cases where CanGraphical will never turn
TRUE. To catch these, add a timeout and fall back to simply trying to
bring seat0 up after 10 seconds. When we do so, go directly for the X11
fallback as wayland is unlikely to be functional.
Fixes: #662
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We used to check the session type when enumerating the seats at startup
(and on VT switch). However, this misses cases where seats are added
dynamically (such as at boot time).
Simply move the check into create_display and pass in the failure count
so that it can handle the X11 fallback when wayland failed to come up.
Related: #662
|
| | |
| |
| |
| | |
Also drop the return value as it is never used.
|
| |/
|
|
| |
It's deprecated now, and always returns TRUE.
|
| |\
| |
| |
| |
| | |
meson: Remove unused check-accelerated-dir option and references
See merge request GNOME/gdm!124
|
| |/ |
|
| |
|
|
|
|
|
|
|
| |
openSUSE is preparing the system to have /etc as 'administrator config files'
with system/package config templates shipped in /usr/etc (similar to the
overlay system used by systemd)
Have gdm follow this and try to load files from /etc, if not existing, fallback
to /usr/etc
|
| |\
| |
| |
| |
| |
| |
| | |
gdm-{wayland,x}-session: import PATH from systemd
Closes #385
See merge request GNOME/gdm!92
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In both gdm-wayland-session and gdm-x-session, environment variables
from the systemd user manager are imported, if it is available. Those
environment variables are set up for the session-to-be-spawned, however,
environment variables that the gdm-{wayland,x}-session process itself
has are also inherited to the new session, and they are given preference
over what is imported from systemd.
That is not accidential, the gdm-{wayland,x}-session process has fresh
variables as to what the new user session will be (think $DISPLAY,
$XDG_CURRENT_DESKTOP, etc.) and those should not be overwritten by stale
data from the systemd user manager, who might have those variables still
set from a previous session.
As the gdm-{wayland,x}-session process does not inherit the environment
in which GDM itself is launched, but gets a fresh environment with only
purposefully added variables, this is in general not a problem (i.e.
there are no environment variables from the systemd system instance
overwriting those in our user session).
However, the GDM session worker sets a default fallback PATH for
gdm-{wayland,x}-session. This then gets preferred over whatever the
systemd user manager has, resulting in the session always getting the
fallback PATH.
As GDM probably needs to consider scenarios where no variables can get
imported from the systemd user manager (maybe it is not used at all),
removing the default PATH is not an option. Instead, this commit adds a
list of environment variables declared as fallbacks, for which we the
imported variables _do_ get preference over our own ones. Currently,
this is only PATH.
Closes: https://gitlab.gnome.org/GNOME/gdm/-/issues/385
|
| | |
|
| |\
| |
| |
| |
| | |
data: Invoke xrdb with -nocpp
See merge request GNOME/gdm!126
|
| |/
|
|
|
| |
Not sure why this was missed in 22590328. /etc/X11/Xresources (at least
on Fedora) only sets the libXft hints and doesn't need cpp to do it.
|
| |\
| |
| |
| |
| | |
cleanup: Use more literal errors
See merge request GNOME/gdm!129
|
| |/
|
|
| |
Replace g_set_error with g_set_error_literal where it makes sense.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
session: Threat PAM max retries error as service unavailable
See merge request GNOME/gdm!130
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a service has returned PAM_MAXTRIES error code we should both emit
the error message and also ensure that this service isn't marked as
available again for the current session, to prevent us to restart the
authentication of it.
An example of this can be the PAM fprintd module that will return us a
max retries error when the user tried to use his finger more times than
configured. In such scenario we want to both prompt the error to the
user and prevent that this module is used again if the user can still
use other authentication methods.
So add an error specialization for PAM_MAXTRIES and threat it as service
unavailable error when emitting it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
