| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |/
|
|
|
|
|
|
|
|
|
| |
commit f4922c046607c45d76e2911aa8f133d0ad4f9223 tried to
fix an overrun in the code, but it neglected to add
"continue" statements to the loops, so it was stuffing
two different values into the same element of an array,
which leads to the wrong session type getting preference.
This commit fixes that.
|
| |\
| |
| |
| |
| | |
local-display-factory: Fix overrun in session type list generation
See merge request GNOME/gdm!148
|
| |/
|
|
|
|
|
| |
Some confusion in the session type list generation from GNOME/gdm!146,
means we could actually overrun the list.
This commit fixes that.
|
| |\
| |
| |
| |
| | |
Support AccountsService Sesson and SessionType properties
See merge request GNOME/gdm!147
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |\
| |
| |
| |
| | |
local-display-factory: Provide more flexibility for configuring display server
See merge request GNOME/gdm!146
|
| | |
| |
| |
| |
| |
| |
| |
| | |
NVidia's wayland story is in a lot better shape these days, so
disabling wayland entirely by default is a big too much.
This commit changes the udev rule to just default to Xorg on single
GPU nvidia vendor driver systems instead of disabling wayland
|
| | |
| |
| |
| |
| |
| | |
Right now the session list comes out in hash table order.
This commit changes the code to sort by description.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There's currently a way to disable wayland, but no way to disable Xorg.
We currently prefer wayland if it's not disabled, but have no way to
prefer Xorg without disabling wayland entirely.
There's currently no way use legacy Xorg support at all if user display
server support is enabled at a build time.
This commit adds more flexibility to display server selection. It adds
two new keys: XorgEnable and and PreferredDisplayServer.
XorgEnable=false disables Xorg support entirely on seat 0.
PreferredDisplayServer can be set to "wayland", "xorg", "legacy-xorg" or
"none" to select which display server is used by default. If it's set to
"wayland", it will fall back to "xorg". If it's set to "xorg" it will
fall back to "wayland".
|
| |\
| |
| |
| |
| | |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
