summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* local-display-factory: Don't try to respawn displays on shutdownfix-shutdown-crashRay Strode2021-09-152-1/+12
| | | | | | | | | | | 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.
* meson: Update to 41.rc41.rcRay Strode2021-09-061-1/+1
|
* NEWS: Update for releaseRay Strode2021-09-061-0/+8
|
* Merge branch 'fix-fallback-mode' into 'master'Ray Strode2021-09-062-87/+129
|\ | | | | | | | | Some session selection fixes See merge request GNOME/gdm!153
| * daemon: Consolidate session-type and supported-session-types listRay Strode2021-09-061-77/+116
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * daemon: Don't update session type if no saved sessionRay Strode2021-09-061-10/+13
|/ | | | | | | | | 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
* Merge branch 'dev' into 'master'Ray Strode2021-09-061-2/+0
|\ | | | | | | | | session-worker: Set session_vt=0 out of pam uninitialization See merge request GNOME/gdm!152
| * session-worker: Set session_vt=0 out of pam uninitializationChingkai Chu2021-09-061-2/+0
|/ | | | | | | | 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
* Update Uzbek (Latin) translationAkbarkhon Variskhanov2021-09-031-269/+309
|
* meson: Bump to 41.alpha41.alphaRay Strode2021-07-281-1/+1
|
* NEWS: Update for releaseRay Strode2021-07-281-0/+7
|
* Merge branch 'session-selection-again' into 'master'Ray Strode2021-07-282-18/+17
|\ | | | | | | | | Another round of fixes related to the nvidia changes See merge request GNOME/gdm!151
| * session: Fix gdm_session_is_wayland_sessionRay Strode2021-07-281-8/+6
| | | | | | | | | | | | | | | | | | | | 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.
| * manager: Plumb supported-session-types down to the sessionRay Strode2021-07-281-8/+8
| | | | | | | | | | | | | | | | 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.
| * session: Fix operators when computing session dirsRay Strode2021-07-281-2/+3
|/ | | | | | | 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.
* Merge branch 'fix-session-type-selection' into 'master'Ray Strode2021-07-271-0/+2
|\ | | | | | | | | local-display-factory: Add missing continue statements See merge request GNOME/gdm!150
| * local-display-factory: Add missing continue statementsRay Strode2021-07-271-0/+2
|/ | | | | | | | | | | 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.
* Merge branch 'fix-overrun' into 'master'Ray Strode2021-07-221-7/+9
|\ | | | | | | | | local-display-factory: Fix overrun in session type list generation See merge request GNOME/gdm!148
| * local-display-factory: Fix overrun in session type list generationRay Strode2021-07-221-7/+9
|/ | | | | | | Some confusion in the session type list generation from GNOME/gdm!146, means we could actually overrun the list. This commit fixes that.
* Merge branch 'support-accountsservice-session-and-session-type' into 'master'Ray Strode2021-07-225-39/+178
|\ | | | | | | | | Support AccountsService Sesson and SessionType properties See merge request GNOME/gdm!147
| * session: support new accountsservice Session and SessionType propsRay Strode2021-07-225-28/+152
| | | | | | | | | | | | | | | | | | | | 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.
| * worker: don't load user settings for program sessionsRay Strode2021-07-221-11/+26
|/ | | | | We don't need or want the login greeter to access accountsservice for its session name
* Merge branch 'better-nvidia-wayland-support' into 'master'Ray Strode2021-07-229-117/+374
|\ | | | | | | | | local-display-factory: Provide more flexibility for configuring display server See merge request GNOME/gdm!146
| * data: Enable wayland for single GPU vendor nvidia machinesRay Strode2021-07-221-2/+6
| | | | | | | | | | | | | | | | 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
| * libgdm: Sort session listRay Strode2021-07-221-0/+19
| | | | | | | | | | | | Right now the session list comes out in hash table order. This commit changes the code to sort by description.
| * daemon: Provide more flexibility for configuring display serverRay Strode2021-07-228-115/+349
|/ | | | | | | | | | | | | | | | | | | 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".
* Merge branch 'handle-failure-before-display-registration' into 'master'Ray Strode2021-07-221-5/+3
|\ | | | | | | | | display: Handle failure before display registration See merge request GNOME/gdm!145
| * display: Handle failure before display registrationRay Strode2021-07-221-5/+3
|/ | | | | | | | | | | | 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.
* Merge branch 'gdm-runtime-config-end-lines' into 'master'Ray Strode2021-07-141-2/+2
|\ | | | | | | | | gdm-runtime-config: end lines in output See merge request GNOME/gdm!139
| * gdm-runtime-config: end lines in outputPaper2021-07-141-2/+2
|/
* Update Bulgarian translationAlexander Shopov2021-07-111-119/+182
|
* Merge branch 'gbsneto/read-xdg-launch-env' into 'master'Ray Strode2021-07-094-123/+172
|\ | | | | | | | | Read XDG_DATA_DIRS from env.d for initial-setup See merge request GNOME/gdm!140
| * launch-environment: Read XDG_DATA_DIRS from env.d for initial-setupCosimo Cecchi2021-07-094-20/+49
| | | | | | | | | | | | | | | | | | | | | | 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.
| * common: Factor out gdm_load_env_d()Cosimo Cecchi2021-07-093-113/+133
|/ | | | | We need to use this machinery from a second location; as a first step factor it out to gdm-common.
* Merge branch 'fix-libwrap-detection' into 'master'Ray Strode2021-07-091-1/+1
|\ | | | | | | | | meson: Fix libwrap detection See merge request GNOME/gdm!142
| * meson: Fix libwrap detectionBernd Feige2021-07-091-1/+1
|/ | | | Bug: https://bugs.gentoo.org/790671
* Merge branch 'do-not-verificate-too-early' into 'master'Ray Strode2021-07-091-12/+24
|\ | | | | | | | | session: Only emit verification-complete on reauth or after session is opened See merge request GNOME/gdm!143
| * session: Emit session-opened-failed on session failuresMarco Trevisan (Treviño)2021-07-091-1/+13
| | | | | | | | | | | | | | | | 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.
| * session: Only emit verification-complete on reauth or after session is openedMarco Trevisan (Treviño)2021-07-091-11/+11
|/ | | | | | | | | | | | | | | | | | | 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
* Update Russian translationAlexey Rubtsov2021-06-261-1898/+1143
|
* Update Chinese (Taiwan) translationCheng-Chia Tseng2021-06-031-33/+87
|
* Update Occitan translationQuentin PAGÈS2021-05-301-21/+21
|
* Update Portuguese translationHugo Carvalho2021-05-231-100/+92
|
* Update Occitan translationQuentin PAGÈS2021-05-091-75/+129
|
* Update Nepali translationPawan Chitrakar2021-05-011-65/+102
|
* Merge branch 'fix-localedir-summary' into 'master'Benjamin Berg2021-04-301-1/+1
|\ | | | | | | | | meson: Fix localedir summary See merge request GNOME/gdm!138
| * meson: Fix localedir summaryMatt Turner2021-04-291-1/+1
|/ | | | | | | In the commit mentioned below, the actual setting was fixed but the summary was forgotten. Fixes: 5d5bc0f4 ("meson: Fix location of locale directory")
* Update Russian translationStas Solovey2021-04-251-25/+88
|
* Update Slovak translationDušan Kazik2021-04-191-35/+115
|
* Merge branch 'pam-last-password' into 'master'Ray Strode2021-04-181-6/+26
|\ | | | | | | | | | | | | Use the last cryptsetup password with PAM Closes #657 See merge request GNOME/gdm!136
View Lorry Controller Status