| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
local-display-factory: restart greeter session when crashed
See merge request GNOME/gdm!166
|
|/
|
|
|
|
|
| |
When active vt is gdm initial vt, restart greeter session. Avoiding
the blank screen when greeter session crashed.
https://gitlab.gnome.org/GNOME/gdm/-/issues/735
|
|\
| |
| |
| |
| | |
gdm.rules: Keep wayland enabled for simple-framebuffer DRM drivers
See merge request GNOME/gdm!167
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not all DRM drivers are disabled when the nomodeset kernel cmdline option
is used. For example the simpledrm driver that use the system framebuffer
set-up by the bootloader, provides a modesetting interface.
Exclude the DRM drivers that match against the "simple-framebuffer" device
and only disable wayland for platform DRM drivers.
This allows to start a wayland session when nomodeset is used to disable a
platform DRM driver by using the simpledrm driver instead of legacy fbdev
drivers such as efifb, that does not support modsetting and could only be
used with an Xorg session.
|
|\
| |
| |
| |
| | |
daemon: Support X servers built with -Dlisten_tcp=true
See merge request GNOME/gdm!162
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Xorg since version 1.17 doesn't listen to tcp sockets by default
unless it's explicitly built with -Dlisten_tcp=true.
GDM currently assumes X servers 1.17 and later are always built
without specifying -Dlisten_tcp=true and doesn't work properly
otherwise.
This commit enhances GDM to better handle these non-standard builds by
always passing '-nolisten tcp' on the command line when tcp should
be disabled, and likewise always passing '-listen tcp' on the command
line, assuming the X server is new enough to support it, when tcp
should be enabled.
Related #704
|
|\
| |
| |
| |
| |
| |
| | |
local-display-factory: Don't crash if Xorg and Wayland are both unavailable
Closes #739
See merge request GNOME/gdm!160
|
|/
|
|
|
|
|
|
|
|
|
|
| |
At the moment if Wayland doesn't work, the login screen will fall back
to Xorg, and if Xorg doesn't work the login screen will fall back to
Wayland.
But if the fall back choice is disabled explicitly, GDM will just crash.
This commit fixes the crash.
Closes: https://gitlab.gnome.org/GNOME/gdm/-/issues/739
|
|\
| |
| |
| |
| | |
pam-arch: Drop pam_faillock counting from fingerprint and smartcard
See merge request GNOME/gdm!163
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As mentioned in an [fprintd issue comment][1], we need to make sure that
the stack's error status is taken from the main auth module, i.e.
pam_fprintd, otherwise GDM will not behave correctly.
Still use pam_faillock preauth so that we test whether the account is
locked, but don't use authfail/authsucc to log a failure/success so this
stack doesn't participate in triggering the lock.
Ideally we would check which return values we actually want to treat as
a reason to lock the account (e.g. fingerprint mismatch) and which are
neutral (e.g. no fingerprints enrolled), but that's much more effort.
Should fix [FS#71750][2].
[1]: https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/112#note_1016191
[2]: https://bugs.archlinux.org/task/71750
|
|\
| |
| |
| |
| |
| |
| | |
libgdm: Handle GDM_SUPPORTED_SESSION_TYPES being unset
Closes #748
See merge request GNOME/gdm!165
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
If GDM_SUPPORTED_SESSION_TYPES is not set in the environment, calling
any libgdm function which internally calls collect_sessions() will log a
CRITICAL from trying to g_strsplit() a NULL string. This may happen if,
for example, a developer is launching gnome-shell directly, rather than
it being launched by GDM.
Don't try to split the NULL string. The rest of collect_sessions()
already gracefully handles supported_session_types being NULL, so no
further changes are needed to the function.
Fixes: https://gitlab.gnome.org/GNOME/gdm/-/issues/748
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
meson: Fix detection of Xorg versions that need -listen tcp
Closes #704
See merge request GNOME/gdm!161
|
|/
|
|
| |
Closes #704
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
daemon: Infer session type from desktop file if user has no saved session type
Closes #733
See merge request GNOME/gdm!159
|
|/
|
|
|
|
|
|
|
|
| |
The accountsservice user cache file can specify a session type
associated with the saved session. This is optional though. If one
isn't specified GDM needs to figure out the session type based on the
list of preferred session types for the system and the session file
itself.
It was failing to do the latter, though. This commit fixes that.
|
|\
| |
| |
| |
| |
| |
| | |
pam: Drop gdm-pin service
Closes #731
See merge request GNOME/gdm!158
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
gdm-pin was an experimental feature that was going to get added to
gnome-shell many years ago. It never happened and these days it
would probably be implemented a little different anyway.
(It would probably use a gdm pam extension)
There's no point keeping this service file around that we aren't
using, so this commit drops it.
Closes: https://gitlab.gnome.org/GNOME/gdm/-/issues/731
|
| |
|
|\
| |
| |
| |
| | |
xdmcp-display-factory: Set supported session types for XDMCP displays
See merge request GNOME/gdm!157
|
|/
|
|
|
|
|
| |
The lower levels of GDM now expect the session types supported by a
display to be specified up front.
This commit makes sure XDMCP displays do that.
|
|\
| |
| |
| |
| | |
local-display-factory: Don't try to respawn displays on shutdown
See merge request GNOME/gdm!156
|
|/
|
|
|
|
|
|
|
|
|
| |
At the moment in the shutdown path we may try to respawn displays
that just got killed.
The respawning happens when things are half torn down leading to
crashes.
This commit makes sure we turn off the respawn logic in the shutdown
path.
|
|\
| |
| |
| |
| | |
gdm.rules: Keep wayland enabled in all nvidia configurations allowing it
See merge request GNOME/gdm!155
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nvidia drivers since version 470 supports both native wayland and
accelerated Xwayland. The latter also works in hybrid configurations
using nvidia Optimus (the session will run using the main integrated
GPU, but it will be possible to use switcherooctl to run applications
using the discrete nvidia card).
However, the gdm rules were including a line that was supposed to
disable such scenario, but it didn't actually work as expected, so we
can safely remove it, without changing the behavior.
At the same time we can tune the rules so that, when the nvidia-drm
module is loaded, if the driver version is minor than 470, wayland is
disabled.
|
|
|
|
| |
- Translation updates
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Some session selection fixes
See merge request GNOME/gdm!153
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There's currently a bug in computing the session-type to use.
The `i > 0` check means wayland will overwrite x11 in the
transient session type list.
Morever, the separation between "session-type" and
"supported-session-types" is a little redundant. Since
supported-session-types is a sorted list, the first item should
always be the same as "session-type".
This commit addresses the bug and the redundant logic, by computing
the supported session types early in the function and indexing into
it to get the session-type.
A future cleanup could probably get rid of session-type entirely.
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/153
|
|/
|
|
|
|
|
|
|
| |
At the moment we always set the session type when the session name
is read. But users don't always have a session type specified.
If they don't, then don't set the session type.
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/153
|
|\
| |
| |
| |
| | |
session-worker: Set session_vt=0 out of pam uninitialization
See merge request GNOME/gdm!152
|
|/
|
|
|
|
|
|
| |
MR GNOME/gdm!123 moved jump_to_vt and session_vt reseting to a
separate function, so we don't need to reset session_vt in pam
uninitialization.
https://gitlab.gnome.org/GNOME/gdm/-/issues/719
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Another round of fixes related to the nvidia changes
See merge request GNOME/gdm!151
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
gdm_session_is_wayland_session has two problems:
1. it's leaking the full patch returned
2. It's not honoring the supported-session-types
preference ordered list when determining which session to pick.
This commit fixes both issues.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The session code needs to know what session types are supported
for user sessions when deciding which type of session to use at
command generation time.
This commit makes sure that information gets plumbed down.
|
|/
|
|
|
|
|
| |
The loop that computes the list of session directories to check
used the wrong operator, so it was computing the list incorrectly.
This commit fixes that.
|
|\
| |
| |
| |
| | |
local-display-factory: Add missing continue statements
See merge request GNOME/gdm!150
|